-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Centos 7 daemon not working correctly #121
Comments
Cloudprint 0.13 and higher is incompatible with python-daemon <2.0 (b39740d). Check that daemon and pidfile are up-to-date (http://permalink.gmane.org/gmane.linux.debian.devel.python.modules/22964). |
Ok, how do I get a different python-daemon version? I have 2.10... |
Per the link, I'd imagine the fix would be 'pip install -U lockfile'. |
ok, i did update on the lockfile, the dameon, still same errors.... thank you, On Thu, Dec 17, 2015 at 8:31 AM, David Steele [email protected]
|
I installed everything like this:
yum install python python-pip gcc python-devel cups-devel
pip install pycups argparse cloudprint[daemon]
pip install --upgrade cloudprint[daemon]
ran cloudprint, it finds the printers and works with a terminal window up. I have tried putting the startup in the rc.d/rc.local and it won't kick off.. any ideas?
cloudprint -d
Traceback (most recent call last):
File "/bin/cloudprint", line 9, in
load_entry_point('cloudprint==0.14', 'console_scripts', 'cloudprint')()
File "/usr/lib/python2.7/site-packages/cloudprint/cloudprint.py", line 610, in main
timeout=5,
File "/usr/lib/python2.7/site-packages/daemon/pidfile.py", line 43, in init
super(TimeoutPIDLockFile, self).init(path, _args, *_kwargs)
TypeError: init() got an unexpected keyword argument 'timeout'
The text was updated successfully, but these errors were encountered: