> One could brute force the logging issue as follows: > > - setup your LDM to write to ~ldm/logs/ldmd.log (which should be a link > to ~ldm/var/logs/ldmd.log for new versions of the LDM) > > - create a script whose purpose in life is to: > > - stop the LDM > > - rotate the LDM log file; meaning to rename ldmd.log.6 to ldmd.log.7, > ldmd.log.5 to ldmd.log.6, ... ldmd.log to ldmd.log.1 > > This is easily done by 'ldmadmin newlog [-n numlogs] [-l logfile]'. > > - start the LDM > > - run the script from cron at the desired interval (once per day, once every > other day, etc.) The problem is that, unless it receives a HUP signal, the system logging daemon will continue writing to the old LDM log file -- even if that file's been renamed or deleted. Regards, Steve Emmerson Ticket Details =================== Ticket ID: YNE-961543 Department: Support LDM Priority: Normal Status: Closed
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.