On Thu, Jun 4, 2009 at 7:37 PM, Stefan Seyfried<[email protected]> wrote:
> Denys Vlasenko wrote:
>> On Sun, May 31, 2009 at 3:19 PM, Stefan Seyfried <[email protected]> wrote:
>>> It's actually a bad idea to log verbose output to stdout,
>>> so if syslog is enabled, only use syslog.
>>
>> We log it to stderr. Why is it a bad idea?
>
> It gets transmitted to the ftp client and not logged to the stderr of inetd
> (this might be an inetd problem, don't know)
Hmm. I googled for it and inetd indeed redirects stderr to network too
(questionable idea at best, but now it is too late to change that).
> and the ftp clients get confused
> by the protocol violation.
I see. Still, in order to get the bad behavior you described,
you ought to specify *both* -v and -S:
# ftpd --help
BusyBox v1.15.0.svn (2009-06-04 11:36:58 CEST) multi-call binary
Usage: ftpd [-wvS] [-t N] [-T N] [DIR]
FTP server
ftpd should be used as an inetd service.
ftpd's line for inetd.conf:
21 stream tcp nowait root ftpd ftpd /files/to/serve
It also can be ran from tcpsvd:
tcpsvd -vE 0.0.0.0 21 ftpd /files/to/serve
Options:
-w Allow upload
-v Log to stderr
-S Log to syslog
-t,-T Idle and absolute timeouts
DIR Change root to this directory
in other words, user makes a mistake. If he runs ftpd from inetd,
he should not specify -v. If he runs ftpd under tcpsvd, it's ok.
--
vda
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
