Prev: Writeup on `the Slackware way'
Next: why no md5 files for alien packages?
From: Dan C on 17 Jun 2008 15:16
On Tue, 17 Jun 2008 18:59:26 +0000, heavytull wrote:

>> find /etc/rc.d -type f | xargs grep -i cups

> ok i did, it seems that rc.M is loading cups!
> look below

Dude.

If you would just do what I already suggested, it should stop cups from
loading. Here it is again:

(As root):
chmod 644 /etc/rc.d/rc.cups
chmod 644 /etc/rc.d/rc.sysvinit

That's it. Then just reboot. Done.


--
"Bother!" said Pooh, as he put Spanish Fly in Christopher Robin's drink.


From: Kees Theunissen on 18 Jun 2008 17:33
William Hunt wrote:
> On Tue, 17 Jun 2008, heavytull wrote:
>> On Mon, 16 Jun 2008 15:52:21 -0700, William Hunt wrote:
>>> heavytull does not run a standard system, and has trouble relating what
>>> he has done or why he did it (- check his posting history).
>> I'm running a standard slackware now since slack12.0;
>
> ummm, NO, you are NOT running a standard slackware system.
> it is NOT standard slackware to have any files in the sysvinit
> directories /etc/rc.d/rc[123456].d/ directories. It is NOT
> standard slackware to have a /etc/rc.d/init.d/ directory.
>
Don't be too sure about this last claim:

kees(a)lankhmar:~$ cd /var/log/packages/
kees(a)lankhmar:/var/log/packages$ grep '^etc/rc\.d/init\.d' *
sysvinit-functions-8.53-i486-2:etc/rc.d/init.d/
sysvinit-functions-8.53-i486-2:etc/rc.d/init.d/README.functions
sysvinit-functions-8.53-i486-2:etc/rc.d/init.d/functions

(Checked this on Slackware 12.0 and 12.1. The output was identical
in both cases.)

But a standard Slackware cups package certainly won't install any
component in /etc/rc.d/init.d or /etc/rc.d/rc[123456].d

[ ... snip ... ]

> Look again, this time more carefully: don't you see all the
> files in /etc/rc.d/rc[123456].d/ and /etc/rc.d/init.d/ ????
>
> ---NONE--- of those files are standard slackware.
> ---ANY--- of those files could be causing your symptoms.
>
> Dan C. gave you good advice - use it.
> If Dan C's advice leads to any unexpected side-effects,
> then it is easily reversed with a 'chmod a-x', so there
> is little risk. --IF-- it causes unexpected side-effects,
> then your /etc/rc.d/ is even more non-standard and even more
> screwed up than you have already told us.

As your current intention is to run a standard Slackware system there
is probably no useful content at all in those directories, other than
/etc/rc.d/init.d/README.functions and rc.d/init.d/functions, but only
leftovers from formerly experiments. These leftovers only cause trouble.

First follow Dan C's advice. If there are no side-effects then you
might want to cleanup those directories.
The easy way to cleanup is:
-- first (as root): rm -rf /etc/rc.d/int.d /etc/rc.d/rc?.d
-- after that either uninstall or reinstall sysvinit-functions to keep
your directory structure consistent with the installed packages.



Regards,

Kees.

--
Kees Theunissen.
From: William Hunt on 18 Jun 2008 19:38
On Wed, 18 Jun 2008, Kees Theunissen wrote:
> William Hunt wrote:
>> On Tue, 17 Jun 2008, heavytull wrote:
>>> On Mon, 16 Jun 2008 15:52:21 -0700, William Hunt wrote:
[...]
>> ummm, NO, you are NOT running a standard slackware system.
>> it is NOT standard slackware to have any files in the sysvinit
>> directories /etc/rc.d/rc[123456].d/ directories. It is NOT
>> standard slackware to have a /etc/rc.d/init.d/ directory.
>>
> Don't be too sure about this last claim:
> kees(a)lankhmar:~$ cd /var/log/packages/
> kees(a)lankhmar:/var/log/packages$ grep '^etc/rc\.d/init\.d' *
> sysvinit-functions-8.53-i486-2:etc/rc.d/init.d/
> sysvinit-functions-8.53-i486-2:etc/rc.d/init.d/README.functions
> sysvinit-functions-8.53-i486-2:etc/rc.d/init.d/functions

well oopsydoodle - you're right, my bad :*)
I guess i'll have to give the OP a full refund now. :*)


[...]
> First follow Dan C's advice. If there are no side-effects then you
> might want to cleanup those directories.
> The easy way to cleanup is:
> -- first (as root): rm -rf /etc/rc.d/int.d /etc/rc.d/rc?.d
> -- after that either uninstall or reinstall sysvinit-functions to keep
> your directory structure consistent with the installed packages.
>
> Regards,
> Kees.

We can hope so :*)

BW,
--
William Hunt, Portland Oregon USA
From: heavytull on 20 Jun 2008 18:08
On Wed, 18 Jun 2008 12:46:17 -0700, William Hunt wrote:


> ummm, NO, you are NOT running a standard slackware system. it is NOT
> standard slackware to have any files in the sysvinit directories
> /etc/rc.d/rc[123456].d/ directories. It is NOT standard slackware to
> have a /etc/rc.d/init.d/ directory.
>
as minded by someone else, the /etc/rc.d/rc.init is part of slackware,
even the latest.
I said that i was running a standard slackware, but i shoould have said
"To my knowledge I'm running a standard slackware"
I removed (with -rf) the etc/rc.d/rc?.d directories.


>
> The evidence seems to show that your 'uninstall' did not work, leaving
> you with the problems you now face: a boogered-up set of startup
> scripts.
>
>
now I remember, actually there was no uninstall option in the cups
Makefile. I posted a question for how to remove cups from an install from
fresh sources, someone told me to just remove the stuff in /usr/local/cups
i think. but i didn't remove anything in /etc/rc.d/;


>


>> ok i did, it seems that rc.M is running cups! look below
>
> Look again, this time more carefully:
yes actually /etc/rc.d/rc.M doesn't load cups since my /etc/rc.d/rc.cups
is not set for execution.


> don't you see all the files in
> /etc/rc.d/rc[123456].d/ and /etc/rc.d/init.d/ ????
>
> ---NONE--- of those files are standard slackware. ---ANY--- of those
> files could be causing your symptoms.
yes there are files set with the x flag on. As long as there is not script
calling them they shouldn't be loaded. I would prefer find which file is
loading them.
>
> Dan C. gave you good advice
I don't like blind advises.
The /etc/rc.d/rc.sysvinit script is provided with the standard slackware
with the x flag on, so I prefer leave it as is! I want to understand what
is the problem.
Maybe this file was running those rc?.d/S* exec files!! now I removed all
rc?.d files, I will see whether cups is still being loaded at next boot,
if not then something is clearer to me.
Studying the rc.sysvinit file is the 'straight forward' solution, but i'm
a bit lazy now, I don't feel like it.

the last thing:
DanC has an aweful record of trollness on these groups. I personally found
that he allways opts for blind solutions. One may probably have less
problems by always using the standard rules, yes! But ME, I want to
understand the OS I'm running. Problems come, I try to solve. ;)

From: Lew Pitcher on 20 Jun 2008 21:19
In alt.os.linux.slackware, heavytull wrote:

> On Wed, 18 Jun 2008 12:46:17 -0700, William Hunt wrote:
>
>
>> ummm, NO, you are NOT running a standard slackware system. it is NOT
>> standard slackware to have any files in the sysvinit directories
>> /etc/rc.d/rc[123456].d/ directories. It is NOT standard slackware to
>> have a /etc/rc.d/init.d/ directory.

Actually, it is. At least since Slackware 12.0 (Slackware 11.0 lacked the
directory)
~ $ cat /etc/slackware-version && ls -R /etc/rc.d/
Slackware 12.0.0
/etc/rc.d/:
init.d rc.K rc.alsa rc.gpm rc.inet1.conf rc.local
[snip]

/etc/rc.d/init.d:
README.functions functions

~ $ cat /etc/rc.d/init.d/README.functions

If you're reading this in /etc/init.d/, Slackware's real init directory is
/etc/rc.d/. Maybe you already knew this, but it never hurts to say. :-)

This script was taken from Fedora (and is presumably licensed under the
GPL).
While I don't see Slackware init scripts making much use of it (but use it
if you wish), some third party init scripts (such as for commercial
software designed to run on Red Hat based systems) expect this script and
use it in their own init scripts, so it's a good idea to make it available
here.

These functions are provided solely for commercial (or other) software
that expects to find "Red Hat-isms". I wouldn't use them to write new
init scripts (personally), but if you've had experience with them in the
past and like them, by all means feel free.

It's planned to continue support for them.

Does that help?

> as minded by someone else, the /etc/rc.d/rc.init is part of slackware,
> even the latest.

I can't (yet) vouch for Slackware 12.1, but Slackware 12.0 does /not/
use /etc/rc.d/rc.init (nor, as I recall, has any Slackware previous)
~ $ cat /etc/slackware-version ; ls /etc/rc.d/rc.i*
Slackware 12.0.0
/etc/rc.d/rc.inet1 /etc/rc.d/rc.inet2 /etc/rc.d/rc.ip_forward
/etc/rc.d/rc.inet1.conf /etc/rc.d/rc.inetd
Perhaps you confuse /etc/rc.d/rc.inetd with /etc/rc.d/rc.init?

[snip]
--
Lew Pitcher

Master Codewright & JOAT-in-training | Registered Linux User #112576
http://pitcher.digitalfreehold.ca/ | GPG public key available by request
---------- Slackware - Because I know what I'm doing. ------


 |  Next  |  Last
Pages: 1 2 3
Prev: Writeup on `the Slackware way'
Next: why no md5 files for alien packages?