I installed Paldo, discovered that the default setup's not as secure as I'd like (sudo nopasswd by default with ssh running, eww ) and set about disabling services... With limited success. The files controlling daemons seem to be in /etc/default, but there's not a file there for everything in /etc/init.d, and it's not always obvious what to put in the relevant file when you create it. (START_SSH=FALSE? START_SSHD=FALSE?) Granted, I could just use chmod -x on the files in /etc/init.d, but I'm a sucker for doing things the "correct" way.

So... What is the "correct" way to enable/disable services that are enabled by default with no file in /etc/default? If it's to create a file in /etc/default, how do I know what to put in it when the name of the script in /etc/init.d might not be the right thing?

P.S. Other than the sudo nopasswd thing, I'm quite pleased with Paldo; it's easily the fastest Gnome-based distro I've ever used, and seems refreshingly free of the bugs that plague similarly up-to-date distros like Fedora. Also, it gets points in my book for using Epiphany instead of the bloated Firefox by default.

/etc/init.d/rc calls every script in /var/run/rc. In that directory there are the symlinks for the services the system starts automatically at boot so you should just delete the relative symlink (not the script in /etc/init.d!!!).
 
..............................
Running GNU/Linux Paldo 1.18 (unstable). Rock my box!

Okay, thanks!

Update: what you recommended doesn't work. At all. The symlinks are all regenerated on reboot, and as a result all the daemons run.

Hi Gullible Jones,
Could you tell me what exactly is the init script you want to disable that doesn't have a /etc/default configuration so I can investigate more?
 
..............................
OSs: Paldo-testing x86_64 :: HP Pavilion dv9680ez

SSHD in particular, though the symlinks are regenerated for all files in /etc/init.d.

Yep, sorry about that. I didn't notice it to regenerates automatically the symlinks...
 
..............................
Running GNU/Linux Paldo 1.18 (unstable). Rock my box!

The initscripts of paldo have a header that defines what runlevel it shoud start

Code	[In neuem Fenster öffnen]
### BEGIN INIT INFO # Provides: sshd # Required-Start: $network # Required-Stop: $network # Default-Start: 3 4 5 # Default-Stop: 0 1 2 6 ### END INIT INFO

The /etc/init.d/rc seems to look for that header to see if it will start the script or not so if the default runlevel is 5 edit the initscript of sshd and remove the 5 from # Default-Start: 3 4 5

Even though the header are commented it seems that they still count for Init validation
 
..............................
OSs: Paldo-testing x86_64 :: HP Pavilion dv9680ez

Thanks.

Might I suggest to the devs that in the next version, a separate file be used for runlevel configuration so that such data doesn't get overwritten during updates?

Edit: so I modified all the files in init.d that I didn't want autostarting, and then ran upkg-upgrade... And was rather upset to see all my painstaking changes replaced as * in /etc/init.d got shuffled to *.saved. Surely there must be some better way of editing runlevel settings, short of the almighty chmod command?

Anyone? Is there at least some way to merge changes to /etc/init.d scripts so the header isn't changed, instead of just replacing them and making the user do extra work?