SUMMARY:
I just needed to install SunSoft Print Client. Its not enough just to
have the FNS packages on the client. SunSoft print Client is available
at:
http://www.sun.com/smcc/solaris-migration/products/SSPC/sspc.html
During the install, it lets you choose between the NIS+ print tables and
your local definitions.
Many thanks to Benjamin Cline <benji@hnt.com> who not only had the
answer but has a cool Latin quotation in his signature. :)
--+------------------------------------------------------------------- Walter R. Moore - System Administrator moorewr@eckerd.edu http://www.gate.net/~walter
attached mail follows:
Hello Sun-Managers!
Bear with me, I don't even know what information would help me here.
I have a NIS+ group (nas.eckerd.edu) which run Solaris 2.5.1.
We set up the fns context with fncreate:
fncreate -t org org/nas.eckerd.edu./
this set up the printers on all the clients. Now, when I add a printer
to the printserver, the command:
lpset -n fns newprintername
adds the printer to the FNS context and to all the clients. Now here
comes my question:
When I add a computer to the NIS network everything works EXCEPT the
printers. Adding and removing system definitions on the server doesn't
affect the new machines. I tried doing fncreate -t host but FNS reports
that I already have definitions for the host. lpstat -t shows:
|>lpstat -t
|scheduler is running
|no system default destination
|>
Can you tell you me what I'm missing, doing wrong, failing to do, etc.?
Also: A MINI-SUMMARY: Terminal problems in Standalone Boot
Thanks to:
Casper Dik
Shriman Gurung
Karl E. Vogel
for their suggestions.
Casper Dik suggested deleteing /etc/syscon.ioctl. I understand that
this forces the Sun to reinitialize its console vars when it reboots.
This did not change this server's behavior.
Shriman Gurung suggested I check the hard link between
/etc/init.d/keymap and /etc/rcS.d scripts along with their
dependencies. This is always good advice. :) The files are all in
place.
Karl Vogel suggested using 'stty sane' to corect the terminal once I've
logged in. I'll try this.. although it doesn't explain why the problem
exists even in a normal boot (until the 'system is ready' line)
Thanks everyone...
-Walter
--+------------------------------------------------------------------- Walter R. Moore - System Administrator moorewr@eckerd.edu http://www.gate.net/~walter
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:58 CDT