Open nobicycle opened 10 years ago
The device /dev/usblp0 seems to be non accessible by the current user, so there is a chmod or chown needed or a udev rule to make it available to the user which is running the printing service.
The credentials in the ini file is for the partkeeper installation to log in and has nothing to do with your local users.
In PartKeeprPrintingService.ini I entered the login details for my own login, which is in the lp group. When I execute: $ python PartKeeprPrintingService.py Welcome to Printing Service for PartKeepr v0.1
Traceback (most recent call last): File "PartKeeprPrintingService.py", line 22, in
printer = printerClass( printerCfg )
File "/srv/http/partkeeper/src/DeviceRawPrinter.py", line 13, in init
fileStream = open( self.config['device'], 'wb' );
IOError: [Errno 13] Permission denied: '/dev/usblp0
But ignoring that, by grabbing all privileges: $ sudo python PartKeeprPrintingService.py Welcome to Printing Service for PartKeepr v0.1
Connecting to remote side ... We recieved an exception: Login failed: Status code: 404 Sleeping some seconds ...
I wondered if I needed to create a login within Partkeepr matching the ini file. I tried this but the result was the same.
is there any harm if PartKeeprPrintingService.py is backgrounded or put under control as a service? Best wishes