Language Selection

English French German Italian Portuguese Spanish

Upstart or sysvinit - as init.d scripts see it

Filed under
Linux

If Debian is to migrate to upstart on Linux, I expect some init.d scripts to migrate (some of) their operations to upstart job while keeping the init.d for hurd and kfreebsd. The packages with such needs will need a way to get their init.d scripts to behave differently when used with sysvinit and with upstart. Because of this, I had a look at the environment variables set when a init.d script is running under upstart, and when it is not.

With upstart, I notice these environment variables are set when a script is started from rcS.d/ (ignoring some irrelevant ones like COLUMNS):

rest here




More in Tux Machines

6 Reasons Your Favorite Linux OS Is Plagued by Bugs

  • 6 Reasons Your Favorite Linux OS Is Plagued by Bugs
  • I’ve been a long-time GNOME user, but for the past few months, I was in a loving relationship with Elementary OS. I found much to love in the minimalist Linux-based operating system, and I encouraged readers to give it a try. But that has changed. The number of bugs I encountered grew over time, and I’ve recently had enough. As a freelance writer, the only thing I need is a working laptop. If that’s not reliable, then I’m wasting time trying to fix the one tool my job requires.
  • Why do Linux distributions have software bugs?
    Linux is one of the best operating systems around, but no OS is perfect. All operating systems end up having bugs of one kind or another, including your favorite Linux distributions. A writer at MakeUseOf has listed six reasons why Linux distributions often have their share of bugs.

today's howtos

Linux and Linux Foundation

Red Hat and Fedora