Upstart doesn't read and execute job that is a symlink to another filesystem

Solution Verified - Updated -

Issue

  • After booting, upstart (/sbin/init) doesn't see job descriptions stored on other filesystems and linked from a .conf symlink in /etc/init/; however, running initctl reload-configuration after booting makes the job available to upstart and a manual initctl start myjob is successful. Why isn't it automatic?

Environment

  • Red Hat Enterprise Linux 6
  • symlink in /etc/init/ to an upstart job conf on any non-root filesystem

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content