Xref: utzoo comp.unix.sysv386:8236 biz.sco.general:66 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!cass.ma02.bull.com!mips2!bull.bull.fr!corton!mcsun!ukc!pyrltd!trevan!trevor From: trevor@trevan.uucp Newsgroups: comp.unix.sysv386,biz.sco.general Subject: Re: Remote Printing Over SCO TCP/IP? Message-ID: <1991May21.055049.7483@trevan.uucp> Date: 21 May 91 05:50:49 GMT References: <1991May19.204503.1754@rfengr.com> <17043@scorn.sco.COM> Organization: Trevan Lines: 51 paulz@sco.COM (W. Paul Zola) writes: >In article <1991May19.204503.1754@rfengr.com> rfarris@rfengr.com (Rick Farris) writes: >}I'm trying to figure out how to automatically print on a >}printer attached to another host. >} >[details deleted] >} >}-- >}Rick Farris RF Engineering POB M Del Mar, CA 92014 voice (619) 259-6793 >}rfarris@rfengr.com ...!ucsd!serene!rfarris serenity bbs 259-7757 >The following article from the SCO Information Tools database should help >with your problem. I'm posting because I think this may be of general >interest. >################## cut here ################ cut here ################## >How do I set up remote printing with SCO TCP/IP? >KEYWORDS: printer remote lpinit mkdev rcmd >RELEASE: SCO TCP/IP Generic >PROBLEM: How do I set up remote printing with SCO TCP/IP. >SOLUTION: The following steps outline how to set up remote printing > with SCO TCP/IP. > > Device name Dont do this on ODT 1.0. We reported a bug with this method some time ago. the line printer scheduler send a sighup to processes associated with /dev/null when it finishes printing (I thing this is a security feature!). This will kill some of those processes. The work around is to make a special null file ie mknod /dev/lpnull c 4 255 This problem was reported to SCO some months ago so I would like to know if it has been fixed in 1.1. -- regards trevor ------------------------------------------------------------------------------ Trevor Harris UUCP: trevor@trevan.uucp Trevan Designs Limited