SCIENTIFIC-LINUX-USERS Archives

August 2005

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Connie Sieh <[log in to unmask]>
Reply To:
Connie Sieh <[log in to unmask]>
Date:
Thu, 11 Aug 2005 10:14:51 -0500
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (88 lines)
Stephan,

On Thu, 11 Aug 2005, Stephan Wiesand wrote:

> Hi,
> 
> yes, I reported this for the first 3.0.5 release candidate, and the 
> solution is indeed to remove the LSB init info altogether. Trying
> to invalidate it may make things worse - try replacing "BEGIN INIT INFO" 
> with "NO BEGIN INIT INFO", then chkconfig --reset on SL 4.1. Don't do this 
> on production systems, I have no clue how init reacts on the resulting 
> mess.
> 
> And yes, afs is affected. The impact is however quite limited at least on 
> 3.0.5. On 4.1 it's a bit worse (the K01afs in all run levels may
> terminate some processes much too early and not as cleanly as the should).
> This had escaped my attention. We should probably do something about it.

Suggestions?
Still have time to fix 41 x86_64.

-Connie Sieh
> 
> Cheers,
>  	Stephan
> 
> On Thu, 11 Aug 2005, Valery Mitsyn wrote:
> 
> > Hi All,
> >
> > for services in /etc/rc.d/init.d with SuSE compatible part like:
> > ### BEGIN INIT INFO
> > .
> > .
> > .
> > chkconfig <service> reset
> > will set both start and stop priority to 50 on SL305,
> > and start=99, stop=50 on SL41. If one broke compatibilities
> > by (for example) inserting addition "-" in
> > # Required-Start:
> > # Required-Stop:
> > things will going better.
> > On SL41.
> > --------------------------------------------------
> > chkconfig pcp reset
> >
> > find /etc/rc.d -name \*pcp
> > /etc/rc.d/rc4.d/S99pcp
> > /etc/rc.d/rc6.d/K50pcp
> > /etc/rc.d/rc5.d/S99pcp
> > /etc/rc.d/rc0.d/K50pcp
> > /etc/rc.d/init.d/pcp
> > /etc/rc.d/rc3.d/S99pcp
> > /etc/rc.d/rc1.d/K50pcp
> > /etc/rc.d/rc2.d/S99pcp
> >
> > perl -pi -e "s|# Required-|# Required--|g" \
> > /etc/rc.d/init.d/pcp
> >
> > chkconfig pcp reset
> >
> > find /etc/rc.d -name \*pcp
> > /etc/rc.d/rc4.d/S95pcp
> > /etc/rc.d/rc6.d/K05pcp
> > /etc/rc.d/rc5.d/S95pcp
> > /etc/rc.d/rc0.d/K05pcp
> > /etc/rc.d/init.d/pcp
> > /etc/rc.d/rc3.d/S95pcp
> > /etc/rc.d/rc1.d/K05pcp
> > /etc/rc.d/rc2.d/S95pcp
> > --------------------------------------------------
> > services affected on SL41:
> > grep -l '# Required-' /etc/init.d/*
> > /etc/init.d/afs
> > /etc/init.d/pcp
> > /etc/init.d/pmie
> > and on SL305:
> > /etc/init.d/afs
> > /etc/init.d/kdc
> > /etc/init.d/smartd
> >
> > Can anyone confirm these observations, or this weirdness
> > comes with my environment only?
> >
> >
> 
> 

ATOM RSS1 RSS2