© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Hi,
There are actually two problems in the start script for ushare.
1. It is launched with --background, so all the logs produced by the process on stdout are lost (or at least I could not find where they were sent to) and you can't see what went wrong when it doesn't start. Instead, the ushare -D command already makes the process run in background, and produces logs in /var/log/syslog.
2. uShare needs the configured network interface to be up and running. In recent Ubuntu distributions, network interfaces are no longer managed in sysV init scripts, but with Upstart. I did not find a nice way to ensure that the network interface was up in the sysV script. So I went for upstart.
Attached you will find an upstart script that worked for me (Ubuntu 12.10). If not using eth0 as your network interface you need to change the corresponding line in the script.
Just drop this file into /etc/init
Yann.