Most printers are set up as remote to host 'print' (currently aliases to 'caxton'), this makes administration considerably easier.
When setting up a printer remote to 'print', remember that when configuring a printer on an HP, that since caxton is a Sun, that the remote system must be marked as BSD compatible. Note that this applies to Solaris 1 *and* Solaris 2.
$Header$
@ 1.3 log @*** empty log message *** @ text @d13 7 a19 10Most printers are set up as remote to serv1, this makes administration considerably easier. However VLT would prefer that each host communicates directly with a printer's JetDirect or NetQue interface in order to provide great resiliance. Problems have been encounted setting up certain machines with JetDIrect software, although this has never been investigated.
When setting up a printer remote to serv1, remember to use the "new" name and remember when configuring a printer on an HP, that since serv1 is a Sun, that the remote system must be marked as BSD compatible. Note that this applies to Solaris 1 and Solaris 2.
d44 3 d49 1 a49 2$Header: /home/ct/serco/ahuxley/docs/html/serco-faq/new/network-services/printing/RCS/index.html,v 1.1 1997/06/13 12:34:36 ahuxley Exp $
@ 1.2 log @*** empty log message *** @ text @d44 3 @ 1.1 log @Initial revision @ text @d5 1 a5 1 d41 3 d46 2 a47 1$Header$
@