On Fri, Apr 02, 2004 at 10:23:01AM +0100, Andy Green wrote:
> On Friday 02 April 2004 02:40, Alexander Dalloz wrote:
> >
> > > (you can add that to /etc/rc.local to get it done each boot).
> >
> > That would be very bad style!
>
> Hi Alexander -
>
> > Services are much better controlled using the init script. Therefor make
> > use of "chkconfig xfs on", and "service xfs start" for one time start.
>
> You're clearly right. Unfortunately I often find myself not knowing enough to
> get things working "in good style", then I rely on whatever brute force
> attack I can muster to just get me working so I can go on (to make these
> efforts stick /etc/rc.local is often involved). I have come to recognize
> that the dirty hack by the under-informed has its place in the world :-) As
> I say you're clearly right, thanks to your info I will clean up my dirty hack
> now.
On the positive note Alexander communicated enough information
to diagnose the problem with his:
"I 'fixed' it by starting xfs by hand.
xfs & "
Next is discovery of why xfs was not started and how to get
it to start correctly next time. I think the answer is:
First a "chkconfig --list | grep xfs" to discover if the X font
server 'service' is on. The output should look like:
$ chkconfig --list | grep xfs
xfs 0:off 1:off 2:on 3:on 4:on 5:on 6:off
If xfs is not on at the current run level ("who -r") then
"chkconfig xfs on"
should mark it as 'on' for the expected run levels. Then
"service xfs start"
or perhaps
"service xfs restart"
will check to see if it should be on at this run level and then
restart it.
If it is "on" and fails to start check the logs and perhaps run the
same script by hand that "service" does (/etc/init.d/xfs start) can be
informative
Since 'xfs' is not alone as a service in all this, there is a long
list of "services" that can be researched. The list can be examined:
service --status-all
chkconfig --list
--
T o m M i t c h e l l
/dev/null the ultimate in secure storage.
