On Sun, Oct 16, 2005 at 01:36:46PM +0300, Timo Sirainen wrote:
On Wed, 2005-09-28 at 13:47 -0400, Glenn Leavell wrote:
Where are you logging to? Syslog or some file? Could you try if changing it to other one makes it work again? Also when this happens, could you run "truss -p
" and see if it's still doing write() calls to log? I've been logging to a file. The problem doesn't appear to be present when logging through syslog.
Did you have info_log_path set? Looks like if log_path is set but info_log_path isn't, it breaks. Although with me it crashes instead of stopping writing.
No, I had not set info_log_path, and that was it. After setting it, logging continues to work as expected after a HUP. Thanks!
Glenn
-- Glenn Leavell glenn@usg.edu Office of Information and Instructional Technology Board of Regents of the University System of Georgia