as root insserv -d /etc/init.d/cupsd Then man insserv On Friday 23 January 2004 17:49, Ted Harding wrote:

Hi Folks,

I have lately installed SuSE 8.2 on a colleague's home machine (the beginnings of a conversion from an alien camp, I think).

However, there have been some embarrassments (this is my first installation of 8.2; previous experience being with 5.1 and 7.2) which I have only been able to solve through Unix/Linux knowhow built up over many years, and which would have totally defeated a beginner.

The main remaining issue (so far) is that 'cupsd' is not started up automatically during the boot process.

The printer (a soundly working HP LJ4+) was configured using YaST2, test pages printed successfully, and the configuration was saved. (This was not done at the time the system was first installed: installation took place on one day, and configuration was left for a later day.)

Subsequent attempts to print from a work file using the 'lpr' command did not work. I ascertained that 'cupsd' was not running and, as root, started it from the command line. Then the file printed successfully, as did further printouts made during the same session.

I then re-booted the machine, and found that 'cupsd' was again not running.

I have tried reconfiguring, and have made all sorts of tours through YaST2, without finding any indication of how to solve this problem. Also, the printed manuals give no help. The EnvVar PRINTER="none". The SuSE Support Database has nothing about 'cupsd'.

The only solution so far is for root to start the daemon manually. This should not be necessary.

A further, related, issue. I wondered if the opportunity to edit system configuration files in YaST2 would lead to a way out. While YaST2 offers various system areas for config-file editing, and clicking on these throws up various relevant "Help" windows, not a single file is offered for editing, and no clickable button on the screen does anything meaningful. There is a little window on top of the right-hand panel which looks as though this is where config files might be listed, but this is blank and greyed-out, and inert.

Any help? I'm finding this embarrassing, and indeed don't know what problems may be encountered later (as I say, this sort of thing is beyond a beginner; and I have to make a 45km journey to go and look at it myself ... ).

Presumably there is some file which can be edited with 'vim' in the good old way, to get cupsd starting at boot ... but which one, and how?

With thanks, Ted.

-------------------------------------------------------------------- E-Mail: (Ted Harding) Fax-to-email: +44 (0)870 167 1972 Date: 24-Jan-04 Time: 02:49:05 ------------------------------ XFMail ------------------------------

-- _____________________________________ John Andersen

-----Original Message----- From: (Ted Harding) To: suse-linux-e@suse.com Date: Sat, 24 Jan 2004 02:49:05 -0000 (GMT) Subject: [SLE] cupsd not starting up at boot (8.2)

Hi Folks,

I have lately installed SuSE 8.2 on a colleague's home machine (the beginnings of a conversion from an alien camp, I think).

However, there have been some embarrassments (this is my first installation of 8.2; previous experience being with 5.1 and 7.2) which I have only been able to solve through Unix/Linux knowhow built up over many years, and which would have totally defeated a beginner.

The main remaining issue (so far) is that 'cupsd' is not started up automatically during the boot process.

Go into YaST-->System-->Runlevel editor and make sure it is selected to start during boot. Ken