Hello... I rebooted my computer and to my dismay when the vsftp trys to start in the services manager for Redhat9.1 it says:


vsftpd dead but subsys locked


I've never encountered a prob like that before and I tried going into /var/lock/subsys and renaming vsftpd and re-trying ... but that gives me another error saying that it can't "touch" vsfpd....


Hm.. this kinda hints to me that /var/subsys/ somehow got the wrong permissions set to itself -- I'm afraid to try and chmod it or anything though cause I'm not sure if this is the problem...

Since xinetd is in there... if I fuck that up by changing its permission... I lock out any contact with the outside world...

Please help a newbie... thanks

i've heard of all sorts of really annoying problems coming up in Red Hat - problems too advanced for newbies or even some more experienced people to fix (i myslef experieced these in RH). in my adventures, slackware has been the distribution of choice.
i don't know why you would go around changing file names, especially for stuff the system looks for when it boots. also, it's possible to chmod a file and not it's entire directory, if that's what you were thinking. i was confused with chmod too, when i first started. maybe i should write an article about how to use it.
it seems that you don't know what "touch" means. (maybe you do, but i'll explain it now anyway) when you "touch" something, you create an empty file with that name. so if you were to pass the command "touch filex" you would create an empty file called filex.
please don't take the name of fsck in vain. maybe you thought it was just something that the cool geeks say, but it's actually an invaluable tool for checking file system corruption (fsck - file system check) much like DOS scandisk. let's keep it holy.
as for actually <i>fixing</i> your problem, i don't know. but i told you some other stuff, so there.

Yeah... I've been a user of SSH for years... I know what all those commands mean... I mean I'm in-between a novice & newb at terminals

... and I fixed it... seemed I had to touch the lock file and all is good.... i just didn't wanna make it so my system wouldnt boot since alot of important service-related files are in /var/subsys!!


Anyways... yeah... and as for the fsck that was a cussword that some sort of "cussword filter" obviously seems to have "sensored" the word down to fsck... heh damn vBulliton sensor!