cloudprint Centos 7 daemon not working correctly

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'

Dec 16 '15 22:12 rnichols430

Cloudprint 0.13 and higher is incompatible with python-daemon <2.0 (b39740d2a8e2922749c92514c458a51734).

Check that daemon and pidfile are up-to-date (http://permalink.gmane.org/gmane.linux.debian.devel.python.modules/22964).

Dec 17 '15 02:12 davesteele

Ok, how do I get a different python-daemon version? I have 2.10...

Dec 17 '15 02:12 rnichols430

Per the link, I'd imagine the fix would be 'pip install -U lockfile'.

Dec 17 '15 14:12 davesteele

ok, i did update on the lockfile, the dameon, still same errors....

thank you, ryan nichols

On Thu, Dec 17, 2015 at 8:31 AM, David Steele [email protected] wrote:

Per the link, I'd imagine the fix would be 'pip install -U lockfile'.

— Reply to this email directly or view it on GitHub https://github.com/armooo/cloudprint/issues/121#issuecomment-165465825.

Dec 17 '15 14:12 rnichols430