question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Executable name conflict in Ubuntu 14.04

See original GitHub issue

I had recently faced this issue after installing the reload package through npm using the -g flag.

The executable name, reload, is in conflict with the actually existing reload executable located at /sbin/reload, which belongs to the initctl program suite in Ubuntu 14.04. This causes the system to attempt to run reload at boot with root permissions and consume CPU usage and HDD activity.

Steps to replicate this issue:

  1. sudo npm install -g reload
  2. Reboot system

I don’t know yet what other consequences this might have at system level, as I don’t know which routines are affected by running reload at system boot.

This issue might also affect other versions of Ubuntu, or even other Linux distros.

Issue Analytics

  • State:closed
  • Created 9 years ago
  • Comments:32 (14 by maintainers)

github_iconTop GitHub Comments

2reactions
kethinovcommented, Apr 22, 2017

Yes. It is a system command installed by default on Ubuntu installations:

$ reload --help
Usage: reload [OPTION]... JOB [KEY=VALUE]...
Send HUP signal to job.

Options:
      --session               use existing D-Bus session bus to connect to init daemon (for testing)
      --system                use D-Bus system bus to connect to init daemon
      --dest=NAME             destination well-known name on D-Bus bus
      --user                  run in user mode (as used for user sessions)
  -q, --quiet                 reduce output to errors only
  -v, --verbose               increase output to include informational messages
      --help                  display this help and exit
      --version               output version information and exit

JOB is the name of the job that is to be sent the signal, this may be followed by zero or more environment
variables to distinguish between job instances.
1reaction
ghostcommented, May 2, 2017

Maybe as well as having a note in the readme you should also mention it when the user runs npm install reload -g.

Read more comments on GitHub >

github_iconTop Results From Across the Web

CONFLICT – List filename-conflicts
Conflict is a tool which examines your shell environment variables such as PATH and reports names which are repeated/conflicting.
Read more >
Having trouble to find the node in ubuntu 14.04 after installing
Because of a conflict with another package, the executable from the Ubuntu repositories is called nodejs instead of node. Keep this in mind...
Read more >
Avoiding name clashes for utilities in PATH
1 Answer 1 · Always call your custom scripts with an absolute path, as you yourself suggest, without modifying $PATH . · Make...
Read more >
Choosing between multiple executables with same name in ...
Executables are found in PATH order. You need to prepend ${HOME}/usr/bin to your path, like so: export PATH="${HOME}/usr/bin:$PATH".
Read more >
Conflicts between /usr/bin and /usr/local/bin - linux - Super User
Using this solution is asking for trouble 'cuz /usr/local is designed to override /usr by the FHS. You will lose access to any...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found