Hi,
Well, the problem was that "fbconsole -d :0" was not running on this
particular sun. I have no idea why this was the case. What we did
was to "/etc/init.d/dtlogin stop" followed by a "/etc/init.d/dtlogin
start" which mysteriously started fbconsole again.
Now the problem disappeared when logging in to the local machine.
However: When logging in to a remote machine (which is offered
in the login dialog starting with Solaris 2.6) the problem persists!!
The only countermeasure I could think of, is to avoid that any
messages are written on the console by modifying /etc/syslogd.conf.
In any case: Thanks for the following people for their replies.
I hope that I didn't forget anyone. I'm appending their replies below
followed by my original posting:
Todd Herr <todd_herr@hermes.sra.com>
Harvey Wamboldt <harvey@iotek.ns.ca>
Steve Stady <stevens@vsl.com>
Casper Dik <casper@holland.Sun.COM>
Jonathan.Loh@BankAmerica.com
MaC <kgmcdonald@earthlink.net>
David W. Blaine <blained@gdls.com>
------------------------------------------------------------------
From: Todd Herr <todd_herr@hermes.sra.com>
Try opening a console session (Workspace -> Programs -> Console) and
see if that doesn't fix the problem...
------------------------------------------------------------------
From: Harvey Wamboldt <harvey@iotek.ns.ca>
>From my ~/.dtprofile file:
#######################################################################
###
### Random stdout and stderr output from apps started by Session Mgr
### or by actions via front panel or workspace menu can be directed
### into the user's $HOME/.dt/sessionlogs directory. By default
### this output is not recorded. Instead it is sent off to
### /dev/null (Unix's "nothing" device).
###
### If this random application output is wanted (usually only wanted
### for debugging purposes), commenting out following
### "dtstart_sessionlogfile" lines will send output to your
### $HOME/.dt/sessionlogs directory.
###
### Alternatively, can change "/dev/null" to "/dev/console" to see
### this debugging output on your console device. Can start a
### console via the Workspace programs menu or via Application Mgr's
### Desktop Tools "Terminal Console" icon.
###
#######################################################################
echo "This session log file is currently disabled." >
$dtstart_sessionlogfile
echo "To enable logging, edit $HOME/.dtprofile and" >>
$dtstart_sessionlogfile
echo "remove dtstart_sessionlogfile=/dev/null line." >>
$dtstart_sessionlogfile
export dtstart_sessionlogfile="/dev/null"
Rgds,
------------------------------------------------------------------
From: Steve Stady <stevens@vsl.com>
It sounds to me like someone logged into the console before the CDE
login screen came up. This has been a problem here when someone logs in
as root and starts the dtlogin stuff manually and doesn't log out before
the dtlogin screen comes up. Unfortunately, the only 100% reliable way
of fixing this is to reboot the machine. Sometimes using the 'command
line login' option during a CDE login, and then logging out again will
clear the console device of any processes that have it open.
> He also reports the he's got a /dev/console permission error logged to
> ~/.dt/errrlog. We've compared the /dev/console and /devices/pseudo/cn*
> permissions with my machines (where it works without problems) but
> they are the same.
This sounds like further evidence that some other process already has
/dev/console open and preventing CDE from writing to it.
------------------------------------------------------------------
From: Casper Dik <casper@holland.Sun.COM>
The console messages are uusally logged by a program called
"fbconsole".
Apparently it no longer works correctly on your system.
------------------------------------------------------------------
From: Jonathan.Loh@BankAmerica.com
Try to open a cmdtool -C on startup this should solve it. The -C says make
this the console window.
------------------------------------------------------------------
From: MaC <kgmcdonald@earthlink.net>
You can configure your syslog.conf file to redirect these messages to a
file. Like /var/adm/messages.
------------------------------------------------------------------
From: David W. Blaine <blained@gdls.com>
On the CDE background, right click and select Refresh. To eliminate the console
errors, open a console window and keep it open.
--------------- o r i g i n a l p o s t i n g ------------------
A co-sysadmin here is having the following problem under Solaris 2.6:
After his users log into CDE, console messages cause the CDE desktop
to become garbled. Basically all messages which go to /dev/console
appear in the middle of the CDE desktop in black letters with a white
background destroying the CDE desktop.
I recall that I've seen this before but could not remember what to
do about it?
He also reports the he's got a /dev/console permission error logged to
~/.dt/errrlog. We've compared the /dev/console and /devices/pseudo/cn*
permissions with my machines (where it works without problems) but
they are the same.
Any hints anyone?
--
--------------------------------------------------------------------------
T o m L e i t n e r Dept. of Communications
Graz University of Technology,
e-mail : tom@finwds01.tu-graz.ac.at Inffeldgasse 12
Phone : +43-316-873-7455 A-8010 Graz / Austria / Europe
Fax : +43-316-463-697
Home page : http://wiis.tu-graz.ac.at/people/tom.html
PGP public key on : ftp://wiis.tu-graz.ac.at/pgp-keys/tom.asc or send
mail with subject "get Thomas Leitner" to pgp-public-keys@keys.pgp.net
--------------------------------------------------------------------------
Before we have the paperless office, we have the paperless toilet!
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:53 CDT