Hi,
since the obvious solution (ExecStop) was found to be bad as it introduces a
regression and it is no more even clear on which level it has to be solved
(systemd, openssh in Debian, openssh in Ubuntu) I think this is no more
as-actionable as before.
Sure if someone has the time (or just
yeah, it's specifically restart that we want to check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1913810
Title:
restart doesn't test for syntax errors
Status in
Ideally, this should be supported by systemd somehow. There is this
(old) discussion upstream, which is relevant here:
https://github.com/systemd/systemd/issues/2175
If we introduced the desired behavior by including an ExecStop script to
the systemd unit configuration file, we would introduce a
** Changed in: openssh (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1913810
Title:
restart doesn't test for syntax errors
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1913810
Title:
restart doesn't test for syntax errors
Status in openssh package in Ubuntu:
5 matches
Mail list logo