Please do not reintroduce shell scripts when we don't need them

Posted Feb 10, 2014 10:43 UTC (Mon) by Darkmere (subscriber, #53695)
In reply to: Please do not reintroduce shell scripts when we don't need them by Siosm
Parent article: Systemd programming part 1: modularity and configuration

It used to be that systemctl would throw a big "huh? Whatchatalkingabout?" When you didn't specify .service, which made "systemctl restart sshd" annoying and hard to use. So they made .service be the default.

Maybe it should balk if there's an ambigious selection (".service and .target? I'm not making a choice!" )

Please do not reintroduce shell scripts when we don't need them

Posted Feb 13, 2014 11:12 UTC (Thu) by kisko (guest, #95529) [Link] (3 responses)

In this case sshd would be an ambigious selection because there's also sshd.socket unit present.

Please do not reintroduce shell scripts when we don't need them

Posted Feb 13, 2014 13:02 UTC (Thu) by Darkmere (subscriber, #53695) [Link] (2 responses)

I have to read up more on what socket-activated things I have on my system, going to be interesting I think.

I'm a tad worried that I might have some things socket-activated where I thought they were disabled.

Please do not reintroduce shell scripts when we don't need them

Posted Feb 13, 2014 14:17 UTC (Thu) by mathstuf (subscriber, #69389) [Link] (1 responses)

If you run "systemctl disable sshd", you get a warning that sshd.socket may still cause its activation and a command you can use to disable it as well. I don't know which version this was implemented in, but in pretty sure it was after 204.

Please do not reintroduce shell scripts when we don't need them

Posted Feb 13, 2014 17:13 UTC (Thu) by Darkmere (subscriber, #53695) [Link]

Yep, looking over the socket activations, I found some of my traditional bastards were there and enabled. PCMCIA, iscsi-related things and so on.

Off with their heads! Though I should look a bit at what
Listen: @ISCSIADM_ABSTRACT_NAMESPACE (Stream)
means.