= Сообщение: 42 из 12457 ======================================== ENET.SYSOP = От : Ulrich Schroeter 2:244/1120 11 Sep 13 14:25:26 Кому : Ward Dossche 11 Sep 13 14:25:26 Тема : Nodelist Problem FGHI : area://ENET.SYSOP?msgid=2:244/1120@fidonet+52307fb9 На : area://ENET.SYSOP?msgid=2:292/854+a4003925 = Кодировка сообщения определена как: CP866 ================================== ============================================================================== Hi Ward,
Wednesday September 11 2013 01:05, you wrote to me:
WD> Uli, US>> yup .. the segment.* naming convention did the trick, WD> ... which was necessitated by too many badly-named segments arriving.
here you have 2, probably more options .... but this all depends on what to achieve
1. clean master directory 2. failsafe import of the latest received segment from lower levels
To achieve goal #1, the best is to use makenl's built-in cleanup mechanism To achieve goal #2, requires one more step: check filename extensions of received segments. In case of "out-of-offset" naming convention, correct the filename extension to the upcoming Fridays daynumber.
In contrast to the "extensions" checker, you require a program (if you don't want to manualy cleanup your master directory) that is doing the housekeeping for cleanup of the master directory. So you have the choice to use a probably simplier program that checks for segment filename extensions, or you use a program, that is doing the housekeeping of your master directory. There is a third alternative: send a feature request to the makenl_ng project doing the "extensions" check and correction on-the-fly ,-)