On 2012-12-19 10:25, Gerard Henry wrote:
found another trouble, in the /etc/rc2.d/S99bbinit: + [ -x /var/opt/SUNWbb/root/bb/bin/nscd ] + /usr/sbin/chroot /var/opt/SUNWbb/root /bb/bin/nscd ld.so.1: nscd: fatal: libavl.so.1: open failed: No such file or directory Killed bu libavl is prsent on the machine (comes from SUNWmdb). Does it mean that it is missing in the chroot env ?
Probably so - and you know where to check - /var/opt/SUNWbb/root ;) Alternately, the process may be inheriting an LD_LIBRARY_PATH or an equivalent that points to a (post-chroot) location where the library is not (even if it exists someplace in the chroot env).
it is available in inetd: utrcmd stream tcp nowait,trusted root /opt/SUNWut/lib/in.utrcmdd in.utrcmdd skiosk1-root% /opt/SUNWut/lib/in.utrcmdd /opt/SUNWut/lib/in.utrcmdd: getpeername: Socket operation on non-socket and the Xlib: connection to "skiosk1:3.0" refused by server^M Xlib: Client is not authorized to connect to Server^M /usr/openwin/bin/xrdb: Can't open display 'skiosk1:3'
Are the name services set up correctly (i.e. host names in /etc/hosts and a pointer to these from /etc/nsswitch.conf, and service names for inetd in /etc/services)? Is this host's own name set up correctly (there should be a line in /etc/hosts with a non-loopback IP address which points to the short hostname and FQDN for this machine, as is known from its /etc/nodename and optional /etc/defaultdomain)?
fontpath: parameter not set
This is reminiscent of problems I saw when updating Solaris from 10u4 to 10u6-10u8, some of the packages with fonts became collections of symlinks rather than files, an liveupgrade complained a lot. The resulting FS layout was not what VNC servers liked, likely SRSS also would complain the same (did not have this problem on SRSS). I am not sure I can quickly find the procedure (will post if I do), but there are commands like mkfontpath(?) which rebuild the text files in roots of font directories and list the characteristic properties of fonts. Once these files are valid, not empty and up-to-date, my VNC consoles began working again. Probably, a fresh installation of the Solaris release "from scratch" would not have this problem out of the box, so if you have so many problems anyway - see if you can start anew, and some of your bugs just disappear? Don't forget to write notes to retrace config steps ;) HTH, //Jim _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
