On 02/27/2012 09:54 PM, Cristian Rodríguez wrote:
On 27/02/12 00:53, Lew Wolfgang wrote:
So I need to figure out how to delay sshguard so that it appears later in the boot sequence.
Later is quite vague, do you want it after Susefirewall I presume ?
Right. sshguard needs to start after SuSEfirewall2_setup. The sshguard rpm created /etc/init.d/sshguard and the symlink /etc/init.d/rc3.d/S08sshguard. The firewall setup link is S15SuSEfirewall2_setup. So I moved S08sshguard to S16sshguard and rebooted. But it still doesn't work, S15SuSEfirewall2_setup is being run after S16sshguard. But "systemctl list-units |grep guard" shows: sshguard.service loaded active running LSB: SSHGUARD provides automatic attack blocking So systemd knows about sshguard, but I don't know how it found out about it. Maybe the install rpm? If it found it by scanning the init.d scripts it must be ignoring the "ls" order. My default runlevel is 3. Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org