Yes I enjoy answering my own questions.
This works with the echo test
|
echo "hello there" > /dev/stdout | lpr -P lp2
|
I will test it with Samco and post my results.
On Thu, 2005-10-27 at 11:43 -0600, Roy Souther wrote:
I am setting up printing on a network using LTSP and PPF
http://research.m1stereo.tv/verem/ppf/.
PPF is working great. I am using the static version of ppf and two lib files libstdc++ and libgcc that need to be copied into the LTSP served root directory and I run them from rc.sysinit with the LD_LIBRARY_PATH set to point to the files.
Using an old UNIX program called Samco that insists on printing to /dev/lp? and cannot find any way to make the local device redirect to lpr.
The Samco program has a setting where I can change the device. The default devices are /dev/lp0 and /dev/lp1. When it prints it just sends its raw data to the devices much like echo does when you do this
|
echo "hello lp1" > /dev/lp1
|
I cannot get the source for the Samco program. I need to make anything the program prints go out to the lpr where I can send it to a remote printer that is shared over ppf from a terminal. Lpr is set to use two printers from the terminal. lp2 printer forwards raw data to the ppf at terminal:9100 and lp3 forwards to terminal:9101
One idea is to make Samco print to a device
but I cannot find any way of making lpr take STDIN for the file. I could try making a wrapper script that would do that but I still have another problem. If the Samco is sending data to the lp device just like the command
|
echo "hello lp1" > /dev/lp1
|
then changing the device to a pipe command would do this
echo "hello lp1" > | lpr -P lp2
or
echo "hello lp1" > | lprwrapper lp2
|
Would that work? I don't think I can redirect into a pipe. Is there a better way to redirect from the device to a program like lpr?
_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
signature.asc
Description: This is a digitally signed message part
_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying
