Sponsored Content
Operating Systems Solaris Solaris 8, you boot the system but does not have anything on the screen (not started) Post 302877761 by DR_RALT on Tuesday 3rd of December 2013 09:47:01 AM
Old 12-03-2013
For clarification:
This is the same issue posted by a very hardworking and smart young man who is taking care of the systems. He has recently learned a great deal about Unix and Solaris and we appreciate his help on the ground here.
 

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

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

5. Solaris

Problem with Solaris system on x86. It would not boot again after updates.

Hi All, I have an x86 system which I have just installed Solaris 10 on, I intend to use this as a database server for Oracle, I tried to patch the server with the latest updates from SUN in preparation for the Oracle installation as I wanted to make sure that I was running the latest patches. ... (0 Replies)
Discussion started by: platforminc
0 Replies

6. Solaris

DVD Solaris System Not able to Mount and Boot

Hi, I have a .ISO file of Solaris system burned into a DVD+ROM, and I encounter the following problems, I am using Sun V440 server, (1) Not able to detect the DVD contents under /cdrom. (2) After reboot with this bootable DVD, I get the following errors, ... (1 Reply)
Discussion started by: Paris Heng
1 Replies

7. Solaris

dual boot solaris/solaris zfs file system

Hi, I am running into a some problems creating a dual boot system of 2 solaris instances using ZFS file system and I was wondering if someone can help me out. First some back ground. I have been asked to change the file system of our server from UFS to ZFS. Currently we are using Solaris... (3 Replies)
Discussion started by: estammis
3 Replies

8. UNIX for Dummies Questions & Answers

Show ksh script started on boot

Hi, i need to know, which ksh script are executed on boot (Sun and aix OS). Where can i find it ? (5 Replies)
Discussion started by: nash83
5 Replies

9. Solaris

Solaris partition in boot screen disappeared - F11??

I have a problem where I installed several OSes as partitions on one disk. And suddenly I cannot see Solaris 11.3 in the bios boot screen anymore. I have no clue why. Do anyone have a suggestion so I can dig further somewhere? I first installed Solaris 11.3. Then Windows10 (gaming). Then Linux... (3 Replies)
Discussion started by: kebabbert
3 Replies

10. 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
PCSCD(8)							    PC/SC Lite								  PCSCD(8)

NAME
pcscd - PC/SC Smart Card Daemon SYNOPSIS
pcscd [options] OPTIONS
-a, --apdu log APDUs and SW using the debug method (see --debug). -c, --config file Specifies the file file as an alternate location for /etc/reader.conf. -f, --foreground Runs pcscd in the foreground and sends log messages to stderr instead of syslog(3). -d, --debug use the lowest log level. Any log message of this level or above will be sent to stderr or syslog(3) depending on the use of --fore- ground. --info use info log level. This is the default log level. --error use error log level. --critical use critical log level. The log levels are ordered as: debug < info < error < critical. Use a log level l will log this level and all the levels above it. -h, --help Displays information about the pcscd command line -v, --version Displays the program version number -H, --hotplug Ask pcscd to rescan the USB buses for added or removed readers and re-read the /etc/reader.conf file to detect added or removed non- USB readers (serial or PCMCIA). DESCRIPTION
pcscd is the daemon program for pcsc-lite and the MuscleCard framework. It is a resource manager that coordinates communications with smart card readers and smart cards and cryptographic tokens that are connected to the system. pcscd is normally started at boot time from /etc/init.d/pcscd. It allows applications to access smart cards and readers without knowing details of the card or reader. pcscd coordinates the loading of drivers for card readers. The purpose of pcsc-lite is to provide a cross compatible API (called winscard) for migrating Windows based PC/SC applications to Unix. At startup, pcscd loads the smart card reader drivers specified in the /etc/reader.conf file (or specified using --config file). SERIAL SMART CARD READER DRIVERS
Smart card reader drivers are placed in the /usr/lib64/readers directory. Each driver is simply an .so file. pcscd locates the driver using the /etc/reader.conf file. See the reader.conf(5) manual page for more information. Drivers are available at http://www.muscle- card.com/drivers.html. USB SMART CARD READER DRIVERS
USB smart card reader drivers are located in /usr/lib64/readers directory as a bundle. You shall not add a USB driver in /etc/reader.conf file. FILES
/etc/reader.conf : Reader configuration file /etc/init.d/pcscd : pcscd startup script /var/run/pcscd/pcscd.pid : process id of the running pcscd /usr/lib64/readers : directory containing bundles for USB drivers SEE ALSO
bundleTool(8), reader.conf(5), syslog(3) AUTHORS
David Corcoran <corcoran@musclecard.com> and Ludovic Rousseau <ludovic.rousseau@free.fr> Muscle January 2007 PCSCD(8)
All times are GMT -4. The time now is 11:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy