I am the OP. What I have done is use a neat little utility called cronolog. Basically what we currently have going is a daemon like:
daemon >>output.log 2>&1 & and output.log just gets bigger and bigger until we shut it down, "rm" the output.log (or mv it somewhere), then start up again. Using cronolog, I can do the following instead: (daemon 2>&1) | cronolog output.log.%Y-%m-%d The cronolog program reads stdin and creates output.log.YYYY-MM-DD. At each local midnight, cronolog will close its output and create a new output.log.YYYY-MM-DD based on the new date. This way, we get a daily log and don't need to do anything with the actual daemon. http://sourceforge.net/projects/cronolog -- Q: What do theoretical physicists drink beer from? A: Ein Stein. Maranatha! John McKown ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
