if I was doing it that way I would simply do a mv arerror.log arerror.log.bak, but that would severely limit my ability to keep backups of information that's in that file, the arerror.log file is not constantly being written to, so its ok to move it while the system is up, if it doesn't exist when the system needs to log something, it simply creates a new one...I personally move the error log off into a sub folder and rename it for the month that it contains information for...I keep a history so that I can go back and see what kind of errors I was experiencing in various timeframes.
_____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Wirasat Siddiqi Sent: Wednesday, May 21, 2008 7:53 AM To: arslist@ARSLIST.ORG Subject: Restricting the growth of arerror.log file ** What is the best way to move the arerrror.log file to some archive directory when it becomes a really large file without re-starting the system. What we are doing to move the file when it becomes big is as follows: We are using Linux SUSE 10 OS. cp arerror.log arerror.log.bak cp /dev/null arerror.log Do you think it is the correct way of emptying out arerror.log file? Please advice. Thanks, Wirasat __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
