openssh unix dev - May 2011 - Rationale for an absence of a native file-logging configuration option for OpenSSH-Server

Good afternoon, I wanted to ask quickly about the rationale for not allowing
explicit declaration of a log file to receive logging output. Whilst using
syslogd is convenient for system processes, for short-lived applications,
such as booting an SSH server (and wishing to monitor it) for testing
purposes? having to also configure syslogd to receive output is
inconvenient.

I ask because it seems logical to allow either a native file, or a syslog
type system to be used, and the absence of a native-log-file directive in
the configuration is inconvenient for me.

Sincerely yours, Lee Hambley

On 05/10/2011 10:24 AM, Lee Hambley wrote:
> Good afternoon, I wanted to ask quickly about the rationale for not
allowing
> explicit declaration of a log file to receive logging output. Whilst using
> syslogd is convenient for system processes, for short-lived applications,
> such as booting an SSH server (and wishing to monitor it) for testing
> purposes? having to also configure syslogd to receive output is
> inconvenient.
You can use sshd's -e option to send logs to stderr, while mapping the
stderr file descriptor (fd 2) to whatever native file (or process) you like.

Does this solve your problem?

Note that if you plan to rotate your logs, you may need to restart sshd
at the appropriate time.

hth,

	--dkg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1030 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20110510/08499579/attachment.bin>