Sponsored Content
Top Forums UNIX for Dummies Questions & Answers The Desktop Messaging System Could Not Be Started HP-UX Post 54750 by Perderabo on Monday 23rd of August 2004 11:19:00 AM
Old 08-23-2004
Windows may be providing DNS.

Post the ouput from the following commands:

ls -l /etc/nsswitch.*
uname -a

Also, does "man nsswitch.conf" give you a man page?
 

7 More Discussions You Might Find Interesting

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

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

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

4. Ubuntu

How to Get Started on Ubuntu Desktop for the first time

Hello Everyone, I have been using RHEL from quite a while now on server system, but now i also want to use Linux as my Desktop/Laptop OS on my personal computer. So i downloaded the Ubuntu 12.04 yeserday as i have read alot about it being the most popular Linux Desktop OS. So guys could you... (1 Reply)
Discussion started by: Rohit Bhanot
1 Replies

5. Shell Programming and Scripting

Getting started with windows and screens without desktop environment

Hi there, Hope the title is sufficiently self explaining. I have no idea how to start and where to start. I don't even know what keywords to google for. I need to build a machine : based on Debian without desktop environment with a quite powerful multi-monitor graphic card able to... (9 Replies)
Discussion started by: chebarbudo
9 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
NSCD(8) 						     Linux Programmer's Manual							   NSCD(8)

NAME
/usr/sbin/nscd - name service cache daemon DESCRIPTION
Nscd is a daemon that provides a cache for the most common name service requests. The default configuration file, /etc/nscd.conf, deter- mines the behavior of the cache daemon. See nscd.conf(5). Nscd provides caching for accesses of the passwd(5), group(5), and hosts(5) databases through standard libc interfaces, such as getpw- nam(3), getpwuid(3), getgrnam(3), getgrgid(3), gethostbyname(3), and others. There are two caches for each database: a positive one for items found, and a negative one for items not found. Each cache has a separate TTL (time-to-live) period for its data. Note that the shadow file is specifically not cached. getspnam(3) calls remain uncached as a result. OPTIONS
--help will give you a list with all options and what they do. NOTES
The daemon will try to watch for changes in configuration files appropriate for each database (e.g. /etc/passwd for the passwd database or /etc/hosts and /etc/resolv.conf for the hosts database), and flush the cache when these are changed. However, this will happen only after a short delay (unless the inotify(7) mechanism is available and glibc 2.9 or later is available), and this auto-detection does not cover configuration files required by nonstandard NSS modules, if any are specified in /etc/nsswitch.conf. In that case, you need to run the following command after changing the configuration file of the database so that nscd invalidates its cache: $ nscd -i <database> SEE ALSO
nscd.conf(5), nsswitch.conf(5) COLOPHON
This page is part of release 3.25 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. GNU
2008-12-05 NSCD(8)
All times are GMT -4. The time now is 09:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy