>>> On 5/6/2014 at 11:45 AM, Mark Pace <[email protected]> wrote:
> I
> look in the start script figure out where the messages should be.
> /etc/rc.d/vsftpd
>
> case "$1" in
> start)
> echo -n "Starting vsftpd "
> /sbin/startproc -l /var/log/rcvsftp.log $VSFTPD_BIN
> rc_status -v
> ;;
>
> Look for the log
> sles001:/etc # ls -al /var/log/rcvsftp.log
> -rw-r--r-- 1 root root 0 Jul 2 2010 /var/log/rcvsftp.log
>
> And it has nothing in it and hasn't been touched since 2010.
> There is also nothing in /var/log/messages or /var/log/vsftpd.log about
> this failure.
>
> Any idea why I don't have a log or what could be causing this error?
First, make sure that you know how vsftpd is getting invoked. It could be via
the script in /etc/rc.d, or it could be via xinetd. On my system, it's not
started at all at the moment.
# chkconfig --list vsftpd
vsftpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
xinetd based services:
vsftpd: off
There are several logging related options in the configuration file. By
default, /etc/vsftpd.conf has:
# Log to the syslog daemon instead of using an logfile.
#
syslog_enable=YES
I would change that to NO. I would also uncomment
log_ftp_protocol=YES
xferlog_enable=YES
But, it would likely be a better idea to use "yast ftp-server" to turn on
SSL/TLS and see what changes get made to the configuration file.
Mark Post
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
