On Sun, 15 Aug 2004 18:17:40 -0400 "Alan DeKok" <[EMAIL PROTECTED]> wrote:
> Ok. The issue there is that the log file is probably opened *after* > stdin, stdout, and stderr are closed. So /dev/stderr is a "magic" > file, and doesn't exist any more once stderr is closed. It looks like that indeed. > Why not just use "radiusd -X", and log to stdout? What's so magic > about stderr? There's nothing magic to stderr, I tried stdout but that didn't work, so I tried stderr which didn't work either. I tried "-x" and that works, but that also logs passwords in cleartext. But apparently the options log_file = /dev/stderr log_auth = yes or, like the doc says logdir = stdout don't work properly when stdout or stderr is used as log output. And the deprecated -lstderr or -lstdout don't work either. I tried to run radiusd as root, but the same thing happens (I think that confirms your statement that the logfile is opened after stderr had closed). When I write the logs to a file everything is OK. I'm not a freeradius specialist but it seems to me that this phenomena is a bug ;-) Richard. -- ___________________________________________________________________ Recursion: see recursion +------------------------------------------------------------------+ | Richard Lucassen, Utrecht, Linux 2.4.20 RedHat 7.2 | | The Netherlands i686/1200MHz/768MB | | Public key: http://www.xs4all.nl/~pe1bbf/pubkey.asc | +------------------------------------------------------------------+ - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
