On 2010/11/27 01:32 PM, Alan DeKok wrote:
Another fix would be to add a radmin command to re-open just the log
files.
Squid does something similar.
squid -l logrotate reopens the log files.
--
Johan Meiring
Cape PC Services CC
Tel: (021) 883-8271
Fax: (021) 886-7782
-
List
Hi,
Or to start logging to a central syslog service?
hmm, log to a disk or throw a packet out onto the network using
UDP and hope that it gets to the destination and the remote
logger is working. lets see.. ;-)
alan
-
List info/subscribe/unsubscribe? See
Alan Buxey a.l.m.bu...@lboro.ac.uk wrote:
Or to start logging to a central syslog service?
hmm, log to a disk or throw a packet out onto the network using
UDP and hope that it gets to the destination and the remote
logger is working. lets see.. ;-)
Raw and traditional UDP syslog is
Hi,
Raw and traditional UDP syslog is not the only option. You could also
syslog to a local daemon...
true - but thats another process running on the server that doesnt need to be
:-)
alan
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi,
Before, it wouldn't re-open the file, even if you did HUP it. I'm not
sure why you thought it was rotating the log files before... that just
didn't work. It opened the log file when the server started, and never
touched it again after that.
thats not the behaviour we saw - eg
Hi,
I understand that changing the behavior is unwanted, but is it really
that much of a burden to HUP the server?
yes. and if i read this mailing list history I see plenty of posts saying dont
HUP
it...I dont think all parts of the server update/refresh when HUP'ing still
so a full restart
Hi,
In our log rotation (on CentOS) we use:
prerotate
/sbin/service radiusd stop /dev/null
endscript
postrotate
/sbin/service radiusd start /dev/null
endscript
I know the workarounds - only hope you dont have someone trying
On Sat, Nov 27, 2010 at 04:53:40AM +0100, Alan DeKok wrote:
I understand that changing the behavior is unwanted, but is it really
that much of a burden to HUP the server?
No, I already published updated Debian packages that do the HUP.
They also had to try harder to make sure that the HUP
On Sat, Nov 27, 2010 at 09:06:08AM +, Alan Buxey wrote:
I see plenty of posts saying dont HUP it...I dont think all parts of the
server update/refresh when HUP'ing still so a full restart is the only
clean way anyway.
With regard to log rotation, that's actually contrary to what it should
Josip Rodin wrote:
With regard to log rotation, that's actually contrary to what it should do :)
The HUP not only reopens log files, but it also reopens the configuration.
But if you have a configuration file that the unprivileged FR user can't
read, esp. if it's radiusd.conf :) the reload
Alan Buxey wrote:
yes. and if i read this mailing list history I see plenty of posts saying
dont HUP
it...I dont think all parts of the server update/refresh when HUP'ing still
so a full restart is the only clean way anyway. I understand the issues with
thread-safe
in this context -
Alan Buxey wrote:
but, even worse, doing this flushes the EAP cache for fast session resumption
And breaks any EAP sessions which are in the process of sending
packets back forth.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Alan Buxey a.l.m.bu...@lboro.ac.uk wrote:
...surely whats needed is a logging thread message handler/parser that
the subthreads talk to - like Apache et al do for their log handling?
Or to start logging to a central syslog service?
Cheers
--
Alexander Clouter
.sigmonster says: HELP! MY
hi,
one eagle-eyed member spotted a small issue with our systems after the upgrade
to 2.1.10
(which, frankly I'd overlooked because to me its more important that people can
actually
authenticate and we've got good accounting etc :-) )
anyway, its this.
the standard radius.log file which
Alan Buxey wrote:
one eagle-eyed member spotted a small issue with our systems after the
upgrade to 2.1.10
It's actually in 2.1.9.
the sudden obvious fix is to add the HUP/restart part to the logrotate script
but
we've never ever had to do this in the past...and I'm loathe to do such a
On Fri, 2010-11-26 at 21:08 +, Alan Buxey wrote:
hi,
one eagle-eyed member spotted a small issue with our systems after the
upgrade to 2.1.10
(which, frankly I'd overlooked because to me its more important that people
can actually
authenticate and we've got good accounting etc :-) )
On Fri, Nov 26, 2010 at 10:46:54PM +0100, Alan DeKok wrote:
Alan Buxey wrote:
one eagle-eyed member spotted a small issue with our systems after the
upgrade to 2.1.10
It's actually in 2.1.9.
the sudden obvious fix is to add the HUP/restart part to the logrotate
script but
we've
Josip Rodin wrote:
On Fri, Nov 26, 2010 at 10:46:54PM +0100, Alan DeKok wrote:
Before, it wouldn't re-open the file, even if you did HUP it. I'm not
sure why you thought it was rotating the log files before... that just
didn't work. It opened the log file when the server started, and never
18 matches
Mail list logo
