Service nginx restart

service nginx restart
systemctl restart nginx

Why switch them around?

Attached: SYSTEMD-e1434229775958.gif (1968x639, 40K)

But you can still use service command with systemd

That doesn't answer my question.

Which way is more UNIX?

Attached: 1518144384926.jpg (300x300, 13K)

old bad, new good

command object action
or
command action object?

Because Lennart...

Attached: 18300154_1509808099038661_4894249253951504384_n.jpg (1080x1080, 193K)

>service nginx, restart
>system control, restart nginx

Systems with systemd come with systemctl by default. Service isn't guaranteed to be on every system you touch (that has systemd).
I'd get used to systemctl.

>system control, restart nginx
it makes more sense when spoken aloud, that's literally it, but secretly it's because poettering hates linux users and wants you to suffer every time you want to go from checking status to stopping/restarting/whatever

service --status-all
systemctl list-unit-files --type service

Attached: 1516670365492.gif (500x500, 1.56M)

Yes

systemd-cgls
systemd-cgtop

>systemds implementation of rm -r would recursively remove directories backward
>Lennart claimed it works as POSIX states
>POSIX states that rm -r must ignore ..
What a guy Lennart is, he programmed systemd and ain't afraid of nothing.

Both make sense you nitwit.

fug got me

Attached: CopyQ.Ti1996.png (288x278, 6K)

>sv r nginx
is enough in void

service apache2 restart

Because traditionally, the services implemented the commands, but systemd said "No fuck your bullshit".

You could make nginx restart start your IoT coffee brewer, there's no guarantee of behavior other than convention. Some services implement restart properly, some implement it poorly. That's why you had to do pgrep apache | xargs kill -9 half the time because the initscript didn't implement restart properly and ended up leaking processes.

systemd doesn't tolerate that bullshit and will SIGKILL everything in the cgroup if it doesn't exit.

because restart is a submodule of systemctl, which you give service name as an argument, while service name is a submodule of service, which you give lifetime command as an argument.
duh.

systemshit is a pyramidal scam, the service on top has an NSA backdoor.

Attached: systemd-refugees-welcome-bring-your-family.jpg (695x537, 69K)

jews did systemd

On the upside, jet fuel can't melt systemd.

Lennart Poettering > Red Hat > NSA > Mossad

jews promote systemd by proxy,
nothing to see here,
just install jewbuntu,
goym

so systemd solved halting problem? when does systemd decide when enough is enough and kills a service that's in the middle of controlled shutdown?

man systemd.kill

It can be configured, but it's not as much of a clusterfuck as initscripts where services handroll their own pidfile nonsense.