Hi Gert,
Friday October 25 2013 09:25, you wrote to Andrew Leary:
GA> Hello Andrew!
GA> I thinking on how I best can make makenl running for zone setup.
GA> Where I not have to thinking on if there is old zone segment in the
GA> way for a new make of zone file. 1. so makenl zone not rename the old
GA> zone a new zone segment file with new day in it. like if there is a
GA> old zone file from last run of makenl zone (if zone.291 exist then
GA> keep this file but make a clean new zone.298) or 2. if zone.291 exist
GA> from last week then delete this and make zone.298 before make the new
GA> zone file.
GA> This so I not have to care for checking for old zone files exist be
GA> for run of makenl zone.
don't know how often I've read your message to understand what's your question
is, but probably I've got it ...
with makenl_ng there are two options to define segment files:
segment.
or
segment.*
with
segment.
the segment files have to be in the order of 7-days frequency that fits to
current week. Current (friday) nodelist is nodelist.319
so also all subsegment files have to be .319 ... .318 or .317 or other namings
doesn't work and such files will be ignored completely !
but handling is ... to keep the last weeks nodelist and create this weeks
nodelist. next week, the older list will be cleaned up. so there are no more
than 2 lists (this week and previous week) in your master directory
with
segment.*
you can make daily nodelists .. but the automatic cleanup is disabled.
With segment.* all subsegments with any daynumber .317 or .318 or .319 will be
accepted. But after running 3 or 4 weeks, you have a mass of "old" segments in
your master directory ... so you have to do some manualy cleanup
hope this helps
GA> Take care,
GA> Gert
GA> $ Origin: KofoBBS at ftp://fido1.kofobbs.net (110:300/1)
regards, uli ;-)
---
* Origin: AMBROSIA - Frankfurt/Main - Germany (2:240/1120)
|
