Trying to change my syslog config today this bit me . I couldn't figure
out why my changes weren't working, and since I don't write syslog
filters often I figured I was screwing something up. Turns out they were
fine. /etc/init.d/rsyslog restart was just silently doing nothing.
This is terrabad.
Are all services shipped in Ubuntu packages for 14.04 using these
scripts, rather than the link to upstart-job? Which version of Ubuntu
was that change made? Is this something users can rely upon being
consistent? There's lots of automation code out there that use the old
scripts.
--
You
I see the wiki page mentions Saucy (13.10). Is that the reference point
where this change is in effect?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1311810
Title:
This change was made intentionally according to a policy change:
https://wiki.ubuntu.com/UpstartCompatibleInitScripts
So I'm not going to change openssh itself, nor I think should rsyslog be
changed. However, I believe some of the Upstart folks were looking into
a quite different centralised
I've added a affects openssh-server because I'm seeing that
/etc/init.d/ssh is an init script as well, instead of a link to
/lib/init/upstart-job.
# file /etc/init.d/ssh
/etc/init.d/ssh: POSIX shell script, ASCII text executable
Contains:
check_for_upstart() {
if init_is_upstart; then
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openssh (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
