I could not get vsftpd to start; kept getting the "vsftpd Dead Subsys Locked" error. On doing a Google search, I came across a fix (lost the site unfortunately) and as I recall, it has something to do with copying a file and having the incorrect SElinux settings (I have SElinux disabled).
The fix was to do a fixfiles, relabel (commands that I have never used) or a touch of "/.autorelabel" and rebooting.
It worked, but I have no idea of what I did (my lack of in depth knowledge of Linux).
Todd **
On Mon, 2005-09-12 at 10:30 -0700, Todd Cary wrote:
I could not get vsftpd to start; kept getting the "vsftpd Dead Subsys Locked" error. On doing a Google search, I came across a fix (lost the site unfortunately) and as I recall, it has something to do with copying a file and having the incorrect SElinux settings (I have SElinux disabled).
The fix was to do a fixfiles, relabel (commands that I have never used) or a touch of "/.autorelabel" and rebooting.
It worked, but I have no idea of what I did (my lack of in depth knowledge of Linux).
/etc/rc.sysinit checks for the presence of /.autorelabel on startup, and if found it relabels all the files in the filesystem with their default SELinux file context as per the current policy. Obviously you didn't disable SELinux as effectively as you thought...
How can I make sure SElinux is fully turned off...?
Todd
Ignacio Vazquez-Abrams wrote:
On Mon, 2005-09-12 at 10:30 -0700, Todd Cary wrote:
I could not get vsftpd to start; kept getting the "vsftpd Dead Subsys Locked" error. On doing a Google search, I came across a fix (lost the site unfortunately) and as I recall, it has something to do with copying a file and having the incorrect SElinux settings (I have SElinux disabled).
The fix was to do a fixfiles, relabel (commands that I have never used) or a touch of "/.autorelabel" and rebooting.
It worked, but I have no idea of what I did (my lack of in depth knowledge of Linux).
/etc/rc.sysinit checks for the presence of /.autorelabel on startup, and if found it relabels all the files in the filesystem with their default SELinux file context as per the current policy. Obviously you didn't disable SELinux as effectively as you thought...
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Mon, 2005-09-12 at 16:28 -0700, Todd Cary wrote:
How can I make sure SElinux is fully turned off...?
set:
SELINUX=disabled
in /etc/sysconfig/selinux
Todd
Ignacio Vazquez-Abrams wrote:
On Mon, 2005-09-12 at 10:30 -0700, Todd Cary wrote:
I could not get vsftpd to start; kept getting the "vsftpd Dead Subsys Locked" error. On doing a Google search, I came across a fix (lost the site unfortunately) and as I recall, it has something to do with copying a file and having the incorrect SElinux settings (I have SElinux disabled).
The fix was to do a fixfiles, relabel (commands that I have never used) or a touch of "/.autorelabel" and rebooting.
It worked, but I have no idea of what I did (my lack of in depth knowledge of Linux).
/etc/rc.sysinit checks for the presence of /.autorelabel on startup, and if found it relabels all the files in the filesystem with their default SELinux file context as per the current policy. Obviously you didn't disable SELinux as effectively as you thought...
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Ariste Software 200 D Street Ext Petaluma, CA 94952 (707) 773-4523 _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Mon, 2005-09-12 at 18:32, Johnny Hughes wrote:
On Mon, 2005-09-12 at 16:28 -0700, Todd Cary wrote:
How can I make sure SElinux is fully turned off...?
set:
SELINUX=disabled
in /etc/sysconfig/selinux
And reboot - I don't think you can change this on the fly.
-
Ignacio Vazquez-Abrams -
Johnny Hughes -
Les Mikesell -
Sean O'Connell -
Todd Cary