ltsp 5 usb attached printer problem

[Barry R Cisna]

Hello All,

On a fresh install of CentOS 6 32-bit with SL6.
I have three people that HAVE to have their own usb attached printers.
Each TC has an static ip in dhcpd.conf. When putting in the same
lts.conf configuration for each TC, from a working ltsp4.2,,other than
changing the usb path to /dev/usblp0.
None of the three can i get to work?
When dropping to a shell on each TC I do see /dev/usb/usblp0.
But,,As the TC boots I never see anything in regards to the actual
printer attached for hardware in the scrolling text.
I have tried many variants of the ltsp4.2 and the documented ltsp 5 usb
printer installation in the lts.conf file.

Could someone that has an working usb printer post their lts.conf file
please?

Thank You,
BC

[Jeff Siddall]

Post by Barry R Cisna
Hello All,
On a fresh install of CentOS 6 32-bit with SL6.
I have three people that HAVE to have their own usb attached printers.
Each TC has an static ip in dhcpd.conf. When putting in the same
lts.conf configuration for each TC, from a working ltsp4.2,,other than
changing the usb path to /dev/usblp0.
None of the three can i get to work?
When dropping to a shell on each TC I do see /dev/usb/usblp0.
But,,As the TC boots I never see anything in regards to the actual
printer attached for hardware in the scrolling text.
I have tried many variants of the ltsp4.2 and the documented ltsp 5 usb
printer installation in the lts.conf file.
Could someone that has an working usb printer post their lts.conf file
please?

Barry,

See my post from a couple of weeks back:

Yup. Confirmed. Printing busted in SL6.1 client also. The problem
seemed to be with the jetpipe app. When I try to manually run it on the
client I get:

-bash-4.1# /usr/bin/python /usr/sbin/jetpipe -b 9600 -y 8 -p none -x
/dev/usblp0 9100
Traceback (most recent call last):
File "/usr/sbin/jetpipe", line 45, in <module>
import daemon
ImportError: No module named daemon

However, installing python-daemon in the chroot (part of the epel repo)
seems to have solved it. Looks like the ltsp-client package has a
missing dependency.

Jeff

[Barry Cisna]

Jeff,

Thanks for the info.
Could you give me an 1,,2,,3,,, what the procedure you done to do the
python-daemon into the chroot?
If I simply chroot to the /opt/ltsp dir and do an yum install
python-daemon,,,will the rpm(s) be pulled down and installed as
expected?
Then I am guessing I do the ltsp-update-sshkeys,,and ltsp-update-image
gig?
Then,,after an TC reboot,,is the usb attached printer
detected,,setup,,without any entries in lts.conf?

Thank You,
Barry

[Jeff Siddall]

Post by Barry Cisna
Jeff,
Thanks for the info.
Could you give me an 1,,2,,3,,, what the procedure you done to do the
python-daemon into the chroot?
If I simply chroot to the /opt/ltsp dir and do an yum install
python-daemon,,,will the rpm(s) be pulled down and installed as
expected?
Then I am guessing I do the ltsp-update-sshkeys,,and ltsp-update-image
gig?
Then,,after an TC reboot,,is the usb attached printer
detected,,setup,,without any entries in lts.conf?

I just did a yum install python-daemon in the chroot and printing
started working. Yes, yum pulls down the dependencies, but you need the
epel repo enabled IIRC.

If you use NBD images instead of NFS then you need to update those also.
You shouldn't to run anything else.

Other than the printer device in your lts.conf is all you should need,
something like:

PRINTER_0_DEVICE=/dev/usblp0

Jeff

[Barry R Cisna]

Jeff,

This fixup,,,worked like a charm! The usb printer kicked right in after
the yum install you suggested.
I did mess up,,a bit,,,as I had to wrangle for a bit,,,even after the
yum install.

I have always used in the past in the lts.conf file,,, [ws005], per
client ,,and has worked to add the client variables...
I couldn't get the usb printer to do it's thing. I finally realized I
now have to use [macaddress] for each TC in stead of the 'ol [ws005]
entry.

Guess I'm too old school k12ltsp.
Oh well.

Thank You,
Barry