Added a note to init.md to clarify the .service copy path for Ubuntu because it differs from the described copy path.
Also noted which version of Ubuntu switched to systemd for the default system init to clarify when the systemd installation steps should be used instead of the upstart installation steps for Ubuntu users.
utACK; though a possible suggestion would be to start out with the assumption that someone is using Ubuntu > 15.04, and add a note for older versions.
Or is the /usr/lib/systemd/system path still the default in other Linux distributions, and Ubuntu is the exception here?
Thanks for the feedback! It looks like Ubuntu is the exception to me.
I'm not a Linux expert, but based on the research I just did it looks like /usr/lib/systemd/system is still the default path for most other distributions (making Debian/Ubuntu the exception).
I was trying to keep my change as minimal as possible but I agree that assuming latest and adding notes to the more outdated or non-default options would be clearer. Would it be preferred to change the first comment to this:
NOTE: When installing for systemd in Debian/Ubuntu the .service file needs to be copied to the /lib/systemd/system directory instead.
And to add a second comment in the Upstart section mentioning that it is no longer the default? Like this:
Upstart was the default init system for Debian/Ubuntu versions older than 15.04. If you are using version 15.04 or newer and haven't manually configured upstart you should follow the systemd instructions instead.
When I saw Debian/Ubuntu mentioned in the header for Upstart, I tried those steps first myself before getting stuck.
@DaveFromBinary The updated text seems more user-friendly as well as being completely neutral with regard to a Ubuntu-specific change. So, I think the newer text is better.
Added a note to init.md to clarify the .service copy path for newer versions of Ubuntu because it differs from the described copy path.
Also noted what version of Ubuntu switched to systemd for the default system init.
ACK 4d14d06fcbd63c64257c09ef0a09ad84efdb6d2e
utACK 4d14d06
Not an expert but from my research, on Debian/Ubuntu the package provided unit files go in /lib/systemd/system/ directory, whereas the user provided or any modification to the package provided unit files go in /etc/systemd/system/ directory.
So, on Debian/Ubuntu, I would rather put bitcoind.service in /etc/systemd/system/ directory.
I'm not an expert on Dedian/Ubuntu either but my understanding (and reading of the stackexchange link you provided) is that the package provided files should go in /lib/systemd/system/ which would include bitcoind.service. Whereas configuration files should go in /etc/systemd/system/ like bitcoin.conf.
From what I understand /etc/systemd/system is used to override /(usr)/lib/systemd/system/ The system should not write anything in /etc (in theory), it's our space. I would put the service file to /etc/systemd/system and reserve /lib/systemd/system/ for the system, it has a lot of pre-installed service files (or units to employ the systemd term).
Also, systemd has multiple instances, one for the system, and one instance by user connected. So I am wondering if we can use the user's service manager for managing and configuring the bitcoin service, which will operate on our user's service manager, not the one of the system. But it can cause other headaches. See this link: https://wiki.archlinux.org/index.php/Systemd/User#How_it_works