Not quite a bug, not quite a feature.... hopefully it would be a quick fix:
The log files (stderr.log for example) get locked/closed/something on a server restart:
tail -f stderr.log &
(no more logs from tail show up)
in which case you need to break out of the current tail, and redo:
tail -f stderr.log
and then you can continue following the tail
Not sure how this actually happens, but this doesnt seem to be a common thing among any apps ive tried. I cant think of any where the tail wouldnt keep working.
Anyways, not a huge deal, just a little thing I noticed.
We'll check this out and see there is a work-around on our end.
I can see how this is useful since many log monitors use the tail function.
It does happen with error.log, as LSWS rotates the error log file for each restart. But for stderr.log, "tail -f" works fine after restarts, at least on my test server.
|All times are GMT -7. The time now is 10:47 AM.|