| Summary: | Canon CAPT Printer Daemon ccpd does not start correctly | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Anil Seth <seth.anil> |
| Component: | systemd | Assignee: | Lennart Poettering <lpoetter> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | harald, johannbg, lpoetter, metherid, mschmidt, notting, plautrba |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-06-03 14:18:43 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Anil Seth
2011-06-03 04:46:40 UTC
(In reply to comment #0) > 2.add /etc/init.d/ccdp start to /etc/rc.local Ugh. Can you instead enable ccdp using chkconfig like you would for any other initscript? "systemctl enable ccpd.service" reported that the file was incompatible with chkconfig. But I found a link with the lines to add to make it compatible with chkconfig. The file was for OpenSuse and had the line # Should-Start: $ALL It created links S-1ccpd. So, I just deleted the $all option. It then created the link S50ccpd. The lines added were: ### BEGIN INIT INFO # Provides: ccpd # Required-Start: $local_fs $remote_fs $syslog $network $named # Should-Start: # Required-Stop: $syslog $remote_fs # Default-Start: 3 5 # Default-Stop: 0 1 2 6 # Description: Start Canon Printer Daemon for CUPS ### END INIT INFO` Still, the problem was the same. I then used rc.local as that is the last thing done. I was also confused by cups insisting on adding an additional printer LBP2900-2 for device usb://Canon/LBP2900. But that seems to be harmless. Incidentally, the Canon's printer support of Linux is definitely very-very flaky. It does not seem to handle or report any errors properly. Should not have bought it. I see. The main problem with that initscript is that it's missing a chkconfig line, for instance: # chkconfig: - 90 10 If you add it, "chkconfig --add ccpd" will work and "chkconfig ccpd on" will too. The problem with starting units from other units (rc-local.service is a kind of a unit too) is that it may lead to deadlocks such as the one described in: https://bugzilla.redhat.com/show_bug.cgi?id=690177#c10 (The "--ignore-dependencies" trick should work in your case too. But I really recommend to make ccpd work as a proper initscript instead.) |