Unix init.d script problems

[GoogleCodeExporter]

I just tried a staged 'make install', and noticed it tries to install a
/etc/init.d/boinc-client script.

Problems:
1. The script should probably be named synecd.
2. It currently loads configuration from /etc/default/boinc-client. This
should also be renamed.
3. Executable names (boinc/boinccmd) are hardcoded into the init.d script
and not in the configuration file. I'd move them to the config file, and of
course also fix them (synecd/syneccmd).

Unfortunately, the script is quite long (500 lines) and kinda hard to
understand.

Original issue reported on code.google.com by nicolas....@gmail.com on 29 Sep 2008 at 2:44

[GoogleCodeExporter]

Most init.d services have a different name to the executable. synecdoche-client 
sounds about right.

You may want to find a packaging expert and talk conventions.

Original comment by didacty...@gmail.com on 29 Sep 2008 at 3:20

• Added labels: Milestone-Release0.1
• Removed labels: ****

[GoogleCodeExporter]

I'm considering changing the install makefile so that the init.d script isn't
installed at all. Which basically means, let's temporarily disable the feature
(starting on boot) until it's cleaned up :)

Original comment by nicolas....@gmail.com on 29 Sep 2008 at 3:28

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

I have disabled installing of the init.d script in r387, until I fix it. Bumping
milestone.

Original comment by nicolas....@gmail.com on 29 Sep 2008 at 5:05

• Added labels: Milestone-Release0.2
• Removed labels: Milestone-Release0.1

[GoogleCodeExporter]

I'm starting to think Linux autostart on boot should be handled by the 
distribution
packagers, not us ("upstream"). Thoughts?

Original comment by nicolas....@gmail.com on 20 Jan 2010 at 6:37

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

This issue was updated by revision r1362.

Original comment by nicolas....@gmail.com on 6 Apr 2010 at 1:12

• Changed state: WontFix
• Added labels: ****
• Removed labels: ****