On Mon, 2003-02-03 at 18:37, [EMAIL PROTECTED] wrote:
> Sorry, I didn't put a subject field
>
>
Thats' ok Abe.
what I do with ssh related problems is to start the sshd process
manually in a term with the -d flag. This put sshd in the debug mode
and a buch of stuff gets spit out to the term that never makes in into
the logs. You will first need to stop the normal process with
service sshd stop
current sessions will not be affected.
this is only good for one session and sshd will exit after the session
is terminated. Don't forget to restart sshd
service sshd start
You can also edit /etc/sshd_config and set the loglevel to DEBUG?
replacing ? with 1,2,or 3
from the sshd man page:
LogLevel
Gives the verbosity level that is used when logging messages from
sshd. The possible values are: QUIET, FATAL, ERROR, INFO, VER
BOSE, DEBUG, DEBUG1, DEBUG2 and DEBUG3. The default is INFO.
DEBUG and DEBUG1 are equivalent. DEBUG2 and DEBUG3 each specify
higher levels of debugging output. Logging with a DEBUG level
violates the privacy of users and is not recommended.
service sshd restart
will activate the changes
This of course will work for all sessions until you reset the LogLevel
and restart sshd. seems like the output gets put in /var/log/secure but
it might be /var/log/messages
HTH
Bret
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
