Sponsored Content
Top Forums Shell Programming and Scripting The DT messaging system could not be started. Post 303019469 by hicksd8 on Friday 29th of June 2018 03:04:44 PM
Old 06-29-2018
How can root login? Text on the console? Or over the network?

You mention a full drive. What message are you getting? If root can login and open a terminal, you should be able to check that easily.

Code:
df -v

Check /etc/hosts for the hostname and correct ip.
This User Gave Thanks to hicksd8 For This Post:
 

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
TELNETLOGIN(8)						    BSD System Manager's Manual 					    TELNETLOGIN(8)

NAME
telnetlogin -- login wrapper for telnetd SYNOPSIS
telnetlogin [-h host] [-p] [-f username] [username] DESCRIPTION
telnetlogin is a setuid wrapper that runs login(1). It is meant to be invoked by telnetd(8); the idea is to remove the necessity of running telnetd as root. telnetlogin should be installed mode 4750, user root, group telnetd. Then, telnetd may be run from /etc/inetd.conf as user ``nobody'', group ``telnetd'', and with the option -L path-to-telnetlogin. telnetlogin accepts only the subset of options to login(1) shown above, in the order listed. This is the order telnetd 8 normally provides them in. telnetlogin also does sanity checks on the environment variables TERM, and REMOTEHOST. It also insists that the standard input, output, and error streams are open on a terminal, and that it is the process group leader of the foreground process of that terminal. After checking all of these conditions, checking the values of the above environment variables for reasonable values, resetting signal handlers, and so forth, it execs login. SEE ALSO
login(1), inetd.conf(5), inetd(8), telnetd(8) RESTRICTIONS
THIS IS PRESENTLY EXPERIMENTAL CODE; USE WITH CAUTION. HISTORY
telnetlogin was written during the development of NetKit 0.17. Linux NetKit (0.17) April 12, 2000 Linux NetKit (0.17)
All times are GMT -4. The time now is 01:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy