next message in archive
no next message in thread
previous message in archive
previous message in thread
Index of Subjects
Index of Subjects > - I'm adding a 'pick the expiry date' option for those wierd situation > when the office mathematician works it out with a pencil... This is at least in part due to my overhaul of the 'expiries' script. A summary of /those/ changes: - runs nightly (but easy enough to change to any frequency, but plays nicely with others if it runs after linerize) - magic code to guess the expiry date moved up into linerize (redefining %19 of ud6) - expiry/pending notices read in from a file - notices reduced to 4/2 weeks before, expiry date, 2 weeks after notice, 4 weeks after lock - moves .forwards out of the way (moving them back, not yet implemented) - reports to $MEM_CHAIR, office on nightly happenings Since the linerize magic to decide on a expiry date uses explicitly defined expiry dates when they exist (is this outside of CCN?), I though it desirable for this code to move up to linerize initialy, and then have all the code writing to namedb's explicitly define an expiry date. Not only would this reduce processing (before it was done for each record when ever expiries was run, now its for every record nightly), but it would allow for non yearly accounts.
next message in archive
no next message in thread
previous message in archive
previous message in thread
Index of Subjects