Redundant scrips in /etc/init.d?
 

p@pc:/etc/init.d$ uname -rv
2.6.30-1-686 #1 SMP Sat Aug 15 19:11:58 UTC 2009 GNU/Linux
p@pc:/etc/init.d$ ls -l /etc/init.d/proc*
-rwxr-xr-x 1 root root 1308 2009-10-04 01:05 /etc/init.d/procps
-rwxr-xr-x 1 root root 997 2006-09-12 18:42 /etc/init.d/procps.sh

Is removal of procps.sh advisable?

Thanks, ... Peter E.





--
Google "pathology workshop"


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Redundant scrips in /etc/init.d?
 

peasthope@shaw.ca wrote at 2009-11-13 12:13 -0600:
> p@pc:/etc/init.d$ uname -rv
> 2.6.30-1-686 #1 SMP Sat Aug 15 19:11:58 UTC 2009 GNU/Linux
> p@pc:/etc/init.d$ ls -l /etc/init.d/proc*
> -rwxr-xr-x 1 root root 1308 2009-10-04 01:05 /etc/init.d/procps
> -rwxr-xr-x 1 root root 997 2006-09-12 18:42 /etc/init.d/procps.sh
>
> Is removal of procps.sh advisable?

Well, on my system I did a
$ locate procps
and found that procps.sh does not exist here.

I ran
$ dpkg -S /etc/init.d/procps
and learned that the applicable package is procps.

I ran
$ apt-cache policy procps
and learned that I have the stable version 1:3.2.7-11 installed.

You must be running Squeeze. What is the output of
$ dpkg -S /etc/init.d/procps.sh

If it does not belong to a package, I would rename it to procps.sh.bak and then
if nothing breaks (including through a reboot) remove it.