Sponsored Content
Top Forums Shell Programming and Scripting The DT messaging system could not be started. Post 303019644 by Stellaman1977 on Tuesday 3rd of July 2018 08:31:37 AM
Old 07-03-2018
Thanks.. It was the full drive. I was able to clear off a 120MB file and the user accounts started working again.
 

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. UNIX for Advanced & Expert Users

The DT messaging system could not be started

Hello All, I am getting " The DT messaging system could not be started" message when wants to login as root on a box running on tru64 5.1A. /etc/hosts is ok. when i see in .dt/errorlog it shows message server could not be started. Thanks for help. Awadhesh (2 Replies)
Discussion started by: Awadhesh
2 Replies

6. 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

7. 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
GRAB-ACCOUNT(8) 						 chiark utilities						   GRAB-ACCOUNT(8)

NAME
grab-account - add new account synchronised to remote system SYNOPSIS
grab-account local-user source [remote-user] DESCRIPTION
grab-account reconfigures sync-accounts to start synchronising a specified local user (which may not yet exist) from a specified remote system, and then invokes sync-accounts once to synchronise from that source. /etc/sync-accounts/createuser should contain a addhere line in the appropriate source section (ie, after host source). grab-account adds a user local-user [remote=remote-user] directive just before addhere and runs sync-accounts source. EXIT STATUS
0 All went well. any other There were problems. FILES
/etc/sync-accounts; See also sync-accounts(8). ENVIRONMENT
See sync-accounts(8). BUGS
There is no locking of /etc/sync-accounts so do not invoke grab-account from a script, or more than once at a time by hand. Do not edit /etc/sync-accounts by hand and also simultaneously run grab-account. The mechanism involving addhere is suboptimal. This should be done with an include feature in sync-accounts, so that grab-account does not have to edit a configuration file that really belongs to the sysadmin. AUTHOR
grab-account and this manpage are part of the sync-accounts package which was written by Ian Jackson <ian@chiark.greenend.org.uk>. They are Copyright 1999-2000,2002 Ian Jackson <ian@davenant.greenend.org.uk>, and Copyright 2000-2001 nCipher Corporation Ltd. The sync-accounts package is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3, or (at your option) any later version. This is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, consult the Free Software Foundation's website at www.fsf.org, or the GNU Project website at www.gnu.org. SEE ALSO
sync-accounts(8), sync-accounts(5), passwd(5) Greenend 14th July 2002 GRAB-ACCOUNT(8)
All times are GMT -4. The time now is 01:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy