Linux - SoftwareThis 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.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
the files in /var/lock/subsys are created to indicate that the service is running. In case of an unclean shutdown or the service dying prematurely, the corresponding file is not deleted. When you try to start the service again, it will assume it is already running and problems start.
I think I've found it, it only occurs after you've edited the vsftpd.conf file
(usually to put anonymous_enable=NO or tcp_wrappers=NO )
and if you should edit them with an extra character on the end, it stops vsftpd form restarting (silently!).
Go back and edit the conf file to end all lines without spaces on the end
and it restarts fine.
I think this is a vsftpd fault, maybe on the RH9 version only, who should it be fed back to?
Thanks for your replies folks, I have solved the problem.
You can uncomment and alter the lines in the vsftpd.conf file
just DO NOT ADD ANY LINES EXCEPT AT THE END OF THE FILE.
I wanted to lock all ftp users in their home directory, and had to add the line:
when i added this line at the end. Vsftp works perftctly
PS Those who wants a copy of my file. please e-mail me
I Had the same problem with my newly installed RED HAT 9 and I found the solution of my 'vsFTP us dead but subsys is locked' in this topic !
A line was added in the middle of the vsftpd.conf file and it causes all of this !! Removing this line was the solution for me.
The funny thing is that I had the error message in french 'VsFTP est mort mais subsys est verrouille' and I didn't found anything with that sentence on Google. Translating this error message to english bring me to this forum
I wanted to let every know that you must enter any text at the end of the file. I wanted to add a banner to the beginning of logins and when I tried to restart, bam, same error. I yanked the text and moved it to the end, and now everything is happy again. Thanks for the great detailed responses.