This is a discussion on proftpd under xinetd problem within the Gentoo Linux Support forums, part of the Unix Operating Systems category; --> Hi, In /etc/xinetd.d/proftpd I have this: service ftp { flags = REUSE socket_type = stream instances = 30 wait ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi, In /etc/xinetd.d/proftpd I have this: service ftp { flags = REUSE socket_type = stream instances = 30 wait = no user = root server = /usr/sbin/proftpd log_on_success = HOST PID log_on_failure = HOST RECORD disable = no } When starting xinetd i get this error in /var/log/daemon.log: Dec 10 19:12:28 acoon xinetd[17523]: Reading included configuration file: /etc/xinetd.d/proftpd [file=/etc/xinetd.d/proftpd] [line=15] Dec 10 19:12:28 acoon xinetd[17523]: Bad log_on_failure flag: RECORD [file=/etc/xinetd.d/proftpd] [line=13] Dec 10 19:12:28 acoon xinetd[17523]: Error parsing attribute log_on_failure - DISABLING SERVICE [file=/etc/xinetd.d/proftpd] [line=13] What could be wrong? -Thomas |
| |||
| So anyway, it was like, 19:24 CET Dec 10 2003, you know? Oh, and, yeah, Thomas Petersen was all like, "Dude, > log_on_failure = HOST RECORD > Dec 10 19:12:28 acoon xinetd[17523]: Bad log_on_failure flag: RECORD > What could be wrong? I'm just guessing, but it might be the "RECORD" part of the line in your configuration above. Have you considered removing it at all? hth. -- Time flies like an arrow, fruit flies like a banana. Perth ---> * 19:33:00 up 2 days, 46 min, 8 users, load average: 2.38, 2.28, 2.25 $ cat /dev/bollocks Registered Linux user #261729 envisioneer B2B niches |
| ||||
| If I remove that line, it works. But what does that line mean? It must be there for a reason. -Thomas "Johan Lindquist" <spam@smilfinken.net> wrote in message news:ti5ka1-5ei.ln1@news.smilfinken.net... > So anyway, it was like, 19:24 CET Dec 10 2003, you know? Oh, and, yeah, > Thomas Petersen was all like, "Dude, > > > log_on_failure = HOST RECORD > > > Dec 10 19:12:28 acoon xinetd[17523]: Bad log_on_failure flag: RECORD > > > What could be wrong? > > I'm just guessing, but it might be the "RECORD" part of the line in > your configuration above. Have you considered removing it at all? > > hth. > > -- > Time flies like an arrow, fruit flies like a banana. Perth ---> * > 19:33:00 up 2 days, 46 min, 8 users, load average: 2.38, 2.28, 2.25 > $ cat /dev/bollocks Registered Linux user #261729 > envisioneer B2B niches |
| Thread Tools | |
| Display Modes | |
|
|