Re: [Svxlink-devel] Logging Features of Svxlink
Brought to you by:
sm0svx
From: Tobias B. <sm...@us...> - 2006-01-11 17:43:20
|
On Wednesday 11 January 2006 15:38, Tim Miller WB0RXX wrote: > Interestingly enough, I found that sending svxlink a SIGHUP did not work > for some reason, so I used a small script (reset_svxlink) > > killall svxlink > sleep 3 > export ASYNC_AUDIO_NOTRIGGER=3D1 > su svxlink -c "/usr/bin/svxlink --daemon --logfile=3D/var/log/svxlink" > > to do the job. As I recall, using "killall -HUP svxlink" forced logging > to the file "svxlink.1" after logrotate had run. I am not sure why this > was happening, but my hack seems to do the trick. ;-) SIGHUP works great here. Are you sure you have tried it with tha latest=20 version? =46rom your description it sounds like SvxLink is not getting the SIGHUP. T= hen=20 it will continue to write to the same file. It doesn't matter that the name= =20 of the file has changed (to svxlink.1). The name only matters at the time=20 when the file is opened. If SvxLink is getting the SIGHUP signal you should see "SIGHUP received.=20 Reopening logfile" at the end of the old log file and "SIGHUP received.=20 Logfile reopened" at the top of the new log file. 73 de SM0SVX / Tobias |