Sponsored Content
Top Forums UNIX for Advanced & Expert Users The DT messaging system could not be started Post 302269111 by fpmurphy on Tuesday 16th of December 2008 11:44:35 PM
Old 12-17-2008
This message is to do with CDE and it's underlying messaging system i.e ToolTalk. If you are unfamilar with ToolTalk, conceptually it is similar to DBUS on Fedora/Redhat/CentOS. It was developed by Sun.

Generally caused by CDE not being able to write files in a user's home directory. Often caused when a user's directory is NFS mounted. Lots of information and good advise available if you search the Web.
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

The Desktop Messaging System Could Not Be Started HP-UX

Hi People! I've just got a HP-UX system dumped on me. I've started it, followed all the install/setup questions, and everything was going ok, right upto when going into the desktop enviroment I got the message "The Desktop Messaging System Could Not Be Started". Now I've checked the... (8 Replies)
Discussion started by: cpiuk
8 Replies

2. HP-UX

HP VUE Messaginbg system could not be started

hi guys..its been a while since my last post... a friend of mine has a problem with their HP Openview and has the following error: The HP VUE messaging system could not be started. To correct the problem: 1. Choose to return to the login-screen. 2. Select failsafe session.... ... ... (2 Replies)
Discussion started by: inquirer
2 Replies

3. IP Networking

DT messaging could not be started

this id the message i get with a suggestions to check those files: /etc/src.sh /etc/hosts /usr/adm/inetd.sec i have little knowledge of hoe to edit those files/ i went to the etc library and didn't found src.sh file. what should i do? also didn't find the inetd.sec file In the host... (3 Replies)
Discussion started by: amirp
3 Replies

4. Solaris

Solaris 10 CDE problem - The DT messaging system could not be started

A Google search with: +Solaris +"The DT messaging system could not be started" returns 138 hits. All of the relevant possible solutions are in this document. My apologies for such a long document but I thought I would try to minimize the resolution attempts that I've already tried. System... (1 Reply)
Discussion started by: rpollard001
1 Replies

5. Solaris

Solaris 8, you boot the system but does not have anything on the screen (not started)

Greetings to all. I have two computers, Sun Blade 150. the first, had the Solaris 8 system, and that system needed to clone the "second" to start it with the same settings. Use a program to clone the drive, and then have cloned, had the error: Can't read disk label. Can't open disk... (4 Replies)
Discussion started by: feliz-58
4 Replies

6. HP-UX

Help needed HP UX 11.11i new install on C8000 Desktop messaging system error CAN'T FIX

Hi, I have a HP UX C8000 box , have installed 11.11i from 4 x cds numerous times to try to get a functioning Network or to try and get rid of this error on start up, after new install and 1st startup I get an error "The desktop messaging system could not be started" and then advice about... (12 Replies)
Discussion started by: C8000
12 Replies

7. Shell Programming and Scripting

The DT messaging system could not be started.

Good Morning, Users can no longer log into SunBlade 2500 Solaris 9 system (though root still can). Here's what I'm getting and what I've done. I'm most suspicious of the full drive since that pops up twice and I did see one looks full. What's a good way to reduce what's on it?- or.. what else... (2 Replies)
Discussion started by: Stellaman1977
2 Replies
wuzzah(1)							      Wuzzah?								 wuzzah(1)

NAME
wuzzah - keep an eye out for friends on a local system SYNOPSIS
wuzzah [OPTIONS...] DESCRIPTION
wuzzah is a program that just sits around and scans the utmpx entries to watch when your friends log in and out. By default upon invoca- tion, wuzzah looks for the file ${HOME}/.wuzzah, and loads the list of buddies contained therein (which are separated by newlines), and then sits and watches. If no file is found, and no other readable file is specified (see OPTIONS), wuzzah will attempt to just watch for whomever the current uid maps, and failing that will just quit. OPTIONS
-h, --help an informative usage summary, though nothing you don't see here... -a, --all-users watches for all users on the system, period. -c, --exec-cmd=CMD execute CMD upon a login. NOTE: this is done with a call to system(2), so you can do things like piping and whatever else you can do with sh -c -f, --buddy-file=FILE use FILE as buddyfile. naturally FILE must be readable, and consists of usernames, one to a line. optionally, these usernames can be followed by a colon, and then a wuzzah command-line to override wuzzah's behavior for this specific user. -F, --no-buddyfile tells wuzzah to not bother loading any config files. -i, --interval=NUM sleep NUM seconds between each polling -m, --message=STRING use STRING as a message template to greet logged-in buddies. See the section FORMATS for more information. -n, --no-newline don't end the messages with newlines (normally does by default) -o, --process-once scan the login records once, then exit -p, --process-current by default wuzzah doesn't message users who were already logged in when started up. this option overrides such behavior and mes- sages them anyways (only useful with the -w/-c options) -q, --silent don't message buddies when they log in (default). -s, --status-message=STRING use STRING as a template for displaying the status of people logging in and out. See FORMATS for more information. -u, --users=LIST adds every user in LIST (a space/comma/colon separated list of users) to the buddy list -v, --version the current version and copyright. -w, --write-buddies turns on messaging of buddies as they log in. NOTE: this can get quite annoying rather quickly. tune in soon for a less annoying solution FORMATS
message templates can be defined as normal character strings, interspersed with special format characters. format characters consist of a `%', followed by a character, which defines situation-specific data. The current list of these characters is as follows: a the alert character ('a') b the name of the buddy who has logged in/out d the date, currently in HH:MM:SS format h and H the remote hostname or IP address (respectively) of your buddy's login l the line in/out on which the buddy is logged (typically, something like /dev/pts/9 or /dev/ttyS0) m whether or not you have just messaged your buddy (really only useful for the -s option) n an embedded newline character o your buddy's online status ("logged on" or "logged off") u your own username, as can best be determined by the program. EXAMPLES
a simple invocation: username@machine$ wuzzah (13:45:39) foo logged in on :0 (not messaging). (13:45:39) bar logged in on pts/11 (not messaging). Message from username@machine on pts/11 at 14:00 ... (wuzzah) username says: "shoutout to my homie foo." EOF an example with a little more user customization: username@machine$ wuzzah --message="hey, %b, it's %u. nice to see you at %d!" and when foo logs in, foo will get a message like so: Message from username@machine on pts/11 at 14:00 ... hey, foo, it's username. nice to see you at (14:00:00)! EOF FILES
$HOME/.wuzzah the default file containing the list of users to watch BUGS
don't know of any, but reports (and patches too) are always welcome. feel free to send them to the author. AUTHOR
sean finney <seanius@seanius.net> sean finney Sun Nov 17 02:41:45 EST 2002 wuzzah(1)
All times are GMT -4. The time now is 04:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy