Visit Jeremy's Blog.
Go Back > Forums > Linux Forums > Linux - Software
User Name
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.


  Search this Thread
Old 04-08-2003, 08:55 AM   #31
LQ Guru
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu
Posts: 12,612

Rep: Reputation: 68

Does the user/group nobody/nogroup exist? Check /etc/passwd and /etc/group to find out.

And what happens if you change to "DefaultServer on"?

Old 04-08-2003, 10:25 AM   #32
Registered: Aug 2002
Location: St Louis, MO
Distribution: Xubuntu, RHEL, Solaris 10
Posts: 929

Original Poster
Rep: Reputation: 30
I changed DefaultServer to 'on', restarted the service, and it worked! Heavens know why it worked this time, but I can now log on with any of the users on my system ('cept root of course) using my real IP...thank you so much! I really appreciate all of your help!

Old 04-08-2003, 02:28 PM   #33
LQ Guru
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu
Posts: 12,612

Rep: Reputation: 68
Cool! Glad you got it working

Feel free to post back if it starts acting up...

Old 09-24-2003, 06:04 PM   #34
LQ Newbie
Registered: Sep 2003
Location: Kentucky
Posts: 1

Rep: Reputation: 0
If you are using xinetd, which it seems you are from an ealier post, you need to do two things. The fist is to edit the proftpd.conf file to look like this:
# This is a basic ProFTPD configuration file (rename it to
# 'proftpd.conf' for actual use. It establishes a single server
# and a single anonymous login. It assumes that you have a user/group
# "nobody" and "ftp" for normal operation and anon.

ServerName "ProFTPD Default Installation"
ServerType inetd
DefaultServer on

# Port 21 is the standard FTP port.
Port 21
# Umask 022 is a good standard umask to prevent new dirs and #files from being group and world writable.
Umask 022

# To prevent DoS attacks, set the maximum number of child #processes to 30. If you need to allow more than 30 concurrent #connections at once, simply increase this value. Note that this #ONLY works in standalone mode, in inetd mode you should use #an inetd server that allows you to limit maximum number of #processes per service (such as xinetd)
MaxInstances 30

# Set the user and group that the server normally runs at.
User nobody
Group nobody

# Normally, we want files to be overwriteable.
<Directory /*>
AllowOverwrite on

# A basic anonymous configuration, no upload directories.
<Anonymous ~ftp>
User ftp
Group ftp
# We want clients to be able to login with "anonymous" as well as "ftp"
UserAlias anonymous ftp

# Limit the maximum number of anonymous logins
MaxClients 10

# We want 'welcome.msg' displayed at login, and '.message' displayed
# in each newly chdired directory.
DisplayLogin welcome.msg
DisplayFirstChdir .message

# Limit WRITE everywhere in the anonymous chroot
<Limit WRITE>


And the second add a file in /etc/xinetd.d/ called proftpd (no ext.) and in that file you will need the following:
service ftp
flags = REUSE
socket_type = stream
instances = 50
wait = no
user = root
server = /usr/sbin/proftpd
bind = <the-ip-you-wish-to-bind-to>
log_on_success = HOST PID
log_on_failure = HOST RECORD
There are two things to change in the above. The first is the path to the executable proftpd, server =, and the second is the IP address to bind to, bind = .

Once this file exists in /etc/xinetd.d/ the ftp service will start when you boot via xinetd.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
X-server fatal error,KDM refused to start callitdctr Linux - Software 3 07-01-2005 08:46 AM
Start Fresh, but still that EVIL FATAL ERROR TheMadAd19 Linux - Newbie 1 02-27-2005 03:51 PM
Fatal Error, Cant Start X Using SuSE 9.1! Please Help! DozenEggs Linux - Newbie 1 07-24-2004 01:57 PM
XIO: fatal IO error 104. X server would not start after problem with Vmware noodle_mee Linux - Newbie 0 07-07-2004 10:48 PM
Upgraded to new kernel via redhat network and cannot start X. Fatal Server Error. Gen13 Red Hat 5 10-25-2003 12:09 AM

All times are GMT -5. The time now is 06:13 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration