initctl list does not show all jobs from /etc/init

Bug #1501242 reported by AlainKnaff
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upstart (Ubuntu)
New
Undecided
Unassigned

Bug Description

initctl list only shows a handful (16) of jobs of /etc/init/ despite 117 conf files being present.

Some jobs, such as xinetd and winbind cannot be started or stopped using upstart, even though an /etc/init/xinetd.conf and an /etc/init/winbind.conf file exist.

Both files are unmodified since package installation.

Xinetd has been installed for a while, whereas winbind is a fresh installation.

Neither kill -HUP 1 , nor initctl reload, nor initctl reload-configuration causes upstart to notice winbind. No recent log files appear in /var/log/upstart . And xinetd should be listed anyways, this package having been installed for a long time.

# lsb_release -rd
Description: Ubuntu 14.04.3 LTS
Release: 14.04

# apt-cache policy upstart
upstart:
  Installed: 1.12.1-0ubuntu4.2
  Candidate: 1.12.1-0ubuntu4.2
  Version table:
 *** 1.12.1-0ubuntu4.2 0
        500 http://lu.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     1.12.1-0ubuntu4 0
        500 http://lu.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

What I expected to happen: winbind should have become startable right after apt-get install winbind at best, and after kill -HUP 1 the latest. In case of error, appropriate and clear messages should be displayed to stderr (at best), or at least into /var/log/upstart

What happened instead: no way of making upstart notice newly installed packages. And old packages for that matter (xinetd)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.