xfs socket startup fails with strict policy
Leonard den Ottolander
leonard at den.ottolander.nl
Wed Aug 25 23:15:49 UTC 2004
Hi,
> The fact that xfs is not listening on port 7100 is of course expected
> behaviour. The directory /tmp/.font-unix seems to have the wrong
> security context though. Did fixfiles miss this temporary directory?
Not necessarily. Removing it by hand and rebooting doesn't fix the
situation:
root 2372 0.5 0.8 12196 2304 ? Ss 01:11 0:00 /usr/bin/gdm-binary -nodaemon
root 2917 0.1 0.4 5312 1120 ? Ss 01:11 0:00 /bin/sh
/etc/X11/gdm/XKeepsCrashing
root 2934 0.0 0.0 2432 252 ? S 01:11 0:00
/usr/libexec/gdmopen -l /bin/sh -c /etc/X11/gdm/XKeepsCrashing -noopen
root 2947 0.3 0.4 5168 1124 tty8 Ss+ 01:11 0:00 /bin/sh
/etc/X11/gdm/XKeepsCrashing -noopen
root 3007 0.0 0.3 5020 1016 tty8 S+ 01:11 0:00
/usr/bin/dialog --yesno I cannot start the X server (your graphical
interface). It is likely that it is not set up correctly. Would you
like to view the X server output to diagnose the problem? 10 50
> Leonard.
--
mount -t life -o ro /dev/dna /genetic/research
More information about the fedora-selinux-list
mailing list