On Wed, 2003-12-03 at 18:27, Norbert Kamenicky wrote:
> Steven Elling wrote:
>
> >I did some package updates on my machine, installed syslog-ng, removed
> >metalog, removed the metalog init script from the default runlevel and
> >
> >
> The question is, if u did it properly ... probably not
>
> this might be done:
>
> rc-update -d metalog
Did this second.
> emerge -C metalog
Did this first.
> rm /etc/init.d/metalog
Curious 'emerge unmerge' did not remove the init script from
'/etc/init.d/', however, it is not located in any of the runlevels so
rc-update worked.
# ls /etc/runlevels/*/*metalog*
ls: /etc/runlevels/*/*metalog*: No such file or directory
Moving 'metalog' out of '/etc/init.d'...
Running 'depscan.sh'...
* Caching service dependencies... [ ok ]
Hmm, no errors. It seems the service dependency error was caused by
emerge leaving the metalog init script on my system.
Now, why did emerge leave the metalog init script on my system? I did
not make any changes to the metalog init script.
The header in the metalog file is:
# $Header:
/home/cvsroot/gentoo-x86/app-admin/metalog/files/metalog.rc6,v 1.10
2003/02/14 22:08:27 vapier Exp $
-----
genlop shows the following:
$> genlop -u metalog
* app-admin/metalog
Merged at Thu Mar 13 23:07:38 2003 (metalog-0.6-r10)
Merged at Fri Mar 14 01:11:08 2003 (metalog-0.6-r10)
Unmerged at Thu May 1 17:03:40 2003 (metalog-0.6-r10)
metalog: merged totally 2 times.
-----
The dates from genlop are not right but it shows that version 0.6-r10
was the only version installed. So, emerge should of removed the
metalog init script.
If metalog init script was left on the system after an unmerge, then how
many other files are being left on the system by emerge?
--
[EMAIL PROTECTED] mailing list
