Open
Conversation
Contributor
|
I don't think a delay is called for. See the comment on 53b083f0 for a probable fix. |
There was a problem hiding this comment.
I think for --chuid and --group you want to replace $CPNAME with $CPUSER.
Contributor
|
Just in case, this is my upstart script, use as you will: $ cat /etc/init/cloudprint.conf Works great on Trusty! (obviously, change exec line to your install) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I added an optional time.sleep(20) to make it work during system boot using the provided /etc/init.d/cloudprint for ubuntu under a user named cloudprint. The wait is controlled by the new command-line option -w.
I also added system install instructions to the README to create the user and to start cloudprint during boot.
I believe the problem was that, although the network had started, some resource was not yet available e.g. perhaps resolv.conf was not yet populated with DNS IPs from DHCP; I don't like this approach (a hard-coded timer) but it does work on my laptop and on a clean system using http://instantserver.io/.