I got problems with failing start of the service on boot - probably too early without working access to google servers (or name resolution failure, who knows...).
Adding "network-online.target" did not help.
I evenually resolved the problem by adding "Restart=on-failure" and "RestartSec=10" to the "Service" section.
Search Criteria
Package Details: gcp-cups-connector-systemd 1.3-1
| Git Clone URL: | https://aur.archlinux.org/gcp-cups-connector-systemd.git (read-only) |
|---|---|
| Package Base: | gcp-cups-connector-systemd |
| Description: | Systemd startup script for Google CloudPrint CUPS Connector |
| Upstream URL: | None |
| Licenses: | |
| Submitter: | grimsock |
| Maintainer: | grimsock |
| Last Packager: | grimsock |
| Votes: | 5 |
| Popularity: | 0.000015 |
| First Submitted: | 2015-10-15 22:20 |
| Last Updated: | 2018-06-07 11:55 |
Latest Comments
grimsock commented on 2016-10-09 13:40
Anonymous comment on 2016-09-16 13:58
ejona86 commented on 2016-01-17 23:21
It isn't clear where the configuration file should go. It seems like the binary checks in the working directory by default, in which case gcp-cups-connector.config.json would need to be at /. I modified the service to add an ExecStart argument: --config-filename /etc/gcp-cups-connector/gcp-cups-connector.config.json
It would probably be a good idea to create that folder as part of one of the packages so that it could be configured with perms 700 to prevent an oauth token from leaking.
grimsock commented on 2015-10-19 21:52
@mzneverdies fixed
mzneverdies commented on 2015-10-19 15:03
sha1sums fails
@MilanKnizek, sorry for delay. Try now I changed a bit service script