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.

  been there too, names as S-1afs is a bit strange, so
find /etc/rc.d -name '[SK]-?afs -exec rm -f {} \; -print
But workaround with double "-" should do the trick.

>
> 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.

  Agree. It seems to me that affected servises are SL additions only.

>
> 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?
>> 
>> 
>
>

-- 
Best regards,
  Valery Mitsyn