2012/8/29 Fajar A. Nugraha l...@fajar.net
On Wed, Aug 29, 2012 at 9:10 PM, Antonio Modesto
mode...@isimples.com.br wrote:
Hi,
Today I'm rotating my log files with a script that runs every night, the
problem is that it must stop the radiusd process, rename the file,
create a
new one
On Fri, Aug 31, 2012 at 6:54 PM, Antonio Modesto
mode...@isimples.com.br wrote:
2012/8/29 Fajar A. Nugraha l...@fajar.net
On Wed, Aug 29, 2012 at 9:10 PM, Antonio Modesto
mode...@isimples.com.br wrote:
Hi,
Today I'm rotating my log files with a script that runs every night, the
On 31 Aug 2012, at 14:17 , Fajar A. Nugraha wrote:
On Fri, Aug 31, 2012 at 6:54 PM, Antonio Modesto
mode...@isimples.com.br wrote:
2012/8/29 Fajar A. Nugraha l...@fajar.net
On Wed, Aug 29, 2012 at 9:10 PM, Antonio Modesto
mode...@isimples.com.br wrote:
Hi,
Today I'm rotating my log
On 29 Aug 2012, at 15:10, Antonio Modesto mode...@isimples.com.br wrote:
Hi,
Today I'm rotating my log files with a script that runs every night, the
problem is that it must stop the radiusd process, rename the file, create a
new one then start radiusd again. Is there a way to do that
On Wed, Aug 29, 2012 at 9:10 PM, Antonio Modesto
mode...@isimples.com.br wrote:
Hi,
Today I'm rotating my log files with a script that runs every night, the
problem is that it must stop the radiusd process, rename the file, create a
new one then start radiusd again. Is there a way to do that
new...@qip.ru wrote:
Hi all, something strange:
I am trying to setup newsyslog to rotate logs of FreeRADIUS 2.1.11
my setup string is looking like
[code]
/var/log/radius.log freeradius:freeradius 644 7 5 * Z
[/code]
but after rotation no logs are writing to /var/log/radius.log until
Hi,
You need to HUP the server to get it to re-open the logs. This is
normal daemon behavior.
its a behaviour that changed with i think 2.1.10 - before then you could rotate
a log and the daemon would start writing to the new logfile.
we had to adjust our logrotate script to do a restart
alan buxey wrote:
unfortunately this means we lose all the state-less stuff - EAP sessions
being the big one.
Huh? The EAP module isn't re-loaded on HUP. So it's ignored. The
sessions still exist after HUP.
Alan DeKok
-
List info/subscribe/unsubscribe? See
Hi,
On Mon, Apr 30, 2012 at 05:01:19PM +0200, Alan DeKok wrote:
alan buxey wrote:
unfortunately this means we lose all the state-less stuff -
EAP sessions being the big one.
Huh? The EAP module isn't re-loaded on HUP. So it's ignored.
The sessions still exist after HUP.
Alan said
Guy Fraser wrote:
I have not checked in quite a while, but at one point a while back,
I suggested using configurable dynamic log file names, like the detail
files have. I used to use such a beast on a version of Cistron Radius
that I customized, but I ran into problems trying to make it work
barry steyn wrote:
Now in my particular case when newsyslog runs from cron it finds that
radius.log, sqltrace.sql and one of the radacct/*/* files have exceeded
their filesize, so it renames them (*.log.n), touches a new file, in the
case of radius.log sends a SIGHUP to radiusd and then
On 5/18/07, Alan DeKok [EMAIL PROTECTED] wrote:
Jack J Allen wrote:
Now in my particular case when newsyslog runs from cron it finds that
radius.log, sqltrace.sql and one of the radacct/*/* files have exceeded
their filesize, so it renames them (*.log.n), touches a new file, in the
case of
Another solution would be to perform logging via syslog(3), which
absolves radiusd from trapping and handling signals and file handlers.
Syslog-ng already does this very well -- why duplicate all of that code?
~BAS
On Fri, 2007-05-18 at 14:57 +0200, Jack J Allan wrote:
On 5/18/07, Alan DeKok
On 5/18/07, Brian A. Seklecki [EMAIL PROTECTED] wrote:
Another solution would be to perform logging via syslog(3), which
absolves radiusd from trapping and handling signals and file handlers.
Syslog-ng already does this very well -- why duplicate all of that code?
~BAS
I've certainly looked
Brian A. Seklecki wrote:
Another solution would be to perform logging via syslog(3), which
absolves radiusd from trapping and handling signals and file handlers.
Syslog-ng already does this very well -- why duplicate all of that code?
As always, patches are welcome.
Alan DeKok.
--
On Fri, 2007-05-18 at 17:09 +0200, Jack J Allan wrote:
On 5/18/07, Brian A. Seklecki [EMAIL PROTECTED] wrote:
Another solution would be to perform logging via syslog(3),
which
absolves radiusd from trapping and handling signals and file
handlers.
On Fri 18 May 2007, Guy Fraser wrote:
On Fri, 2007-05-18 at 17:09 +0200, Jack J Allan wrote:
On 5/18/07, Brian A. Seklecki [EMAIL PROTECTED] wrote:
Another solution would be to perform logging via syslog(3),
which
absolves radiusd from trapping and handling signals
17 matches
Mail list logo
