There have been some reports of X not starting because xfs silently fails when
it cannot write to its socket (unsticky dir, not writable, no tmp dir, caused
by user/program errors, or fs corruption). It might be a good idea to set
correct ownership/permissions before starting xfs. This patch is doing that.
I'm not sure if xfs is the correct place to do this, perhaps somewhere else
in init.d would be better, but I leave you to decide that.
Danny
--- xfs 2002-09-13 08:49:01.000000000 +0200
+++ xfs 2003-01-17 00:11:39.000000000 +0100
@@ -18,6 +18,12 @@
case "$1" in
start)
gprintf "Starting X Font Server: "
+ #Be sure we can use tmp:
+ if [ \!'find / -perm 1777 -name tmp -user root -group root -type d -maxdepth
1' ] ; then
+ mkdir -p tmp
+ chmod 1777 /tmp
+ chown root.root /tmp
+ fi
rm -fr /tmp/.font-unix
daemon --check xfs xfs -port -1 -daemon -droppriv -user xfs
touch /var/lock/subsys/xfs
