igor
2004-07-07 23:17:09 UTC
I am looking for ideas on how to solve a problem with a nohup.out file
that is growing faster than expected.
While we change to a better logging mechanism we're using the stdout
to dump a bunch of debugging messages (a bunch is actually a lot!!).
Any hows, when the application runs for a few days the nohup.out file
could be 1G in size and to search for something on that file becomes a
pain in the neck.
The way I am doing that is pretty much manually. Stop the app, move
the file out and restart the app (using nohup).
I don't know if any of you guys know a better way to either rotate the
nohup.out (by date or size, don't care) or to redirect the stdout to a
logging application.
I have been looking around in the groups and on the net but can't find
anything that will give me some lights on how to do it.
Ciao,
Igor
that is growing faster than expected.
While we change to a better logging mechanism we're using the stdout
to dump a bunch of debugging messages (a bunch is actually a lot!!).
Any hows, when the application runs for a few days the nohup.out file
could be 1G in size and to search for something on that file becomes a
pain in the neck.
The way I am doing that is pretty much manually. Stop the app, move
the file out and restart the app (using nohup).
I don't know if any of you guys know a better way to either rotate the
nohup.out (by date or size, don't care) or to redirect the stdout to a
logging application.
I have been looking around in the groups and on the net but can't find
anything that will give me some lights on how to do it.
Ciao,
Igor