| Age | Commit message (Collapse) | Author |
|---|
|
Was originally causing some problems with nginx but now they're
unlinked.
|
|
|
|
nginx is getting itself banned by systemctl.
I don't know if the upholds is just super quickly restarting or if
it's mirroring the settings set for anki-sync-server.service but I
figure it's worth a shot changing these settings anyway.
|
|
Testing out how upholds works without being annoying about it.
Currently with the default nginx.service file, the service will fail
and restart really really rapidly causing systemctl to ban it and
prevent it from starting ever again.
This is obviously a problem and resetting it requires you to not just
give it a restart but to infact turn off anki-sync-server completely
so it doesn't try to immediately auto restart nginx.
|
|
network.target should be happening way before multi-user.target
wants so it shouldn't need to be here.
|
|
|
|
Add a stop propagation to nginx for convenience.
Hopefully other services also have an upholds for nginx dependencies so
it'll just restart rather than just kill the server and leave
people wondering.
|
|
|
|
Using `Upholds` here because the anki-sync-service needs nginx for
unchunking purposes as specified in the github project.
I only checked the manual to find this option now so I'm only adding it now.
----
Other ones considered:
`Wants` : This was the default choice but there was an even better
option listed further down the man page.
`Requires` : This server doesn't technically require nginx in order to
fully start itself. It just doesn't fully function without it.
`Requisite` : For the reason above it makes sense then to try and at
least start nginx when starting this service which is what Want does.
`BindsTo` : A superset of `Requires`. Sounds like a nice idea at first
glance but, I think it might help in diagnosing problems if only one or the other
went down rather than both.
|
|
When it works it should work immediately.
When it dies it should probably just stay dead.
|
|
|
|
|
|
|