Sponsored Content
Full Discussion: Help with Solaris 8
Operating Systems Solaris Help with Solaris 8 Post 302990164 by DukeNuke2 on Monday 23rd of January 2017 08:14:46 AM
Old 01-23-2017
Try to run devfsadm -Cv to get rid of device entries that are not used anymore.
 

4 More Discussions You Might Find Interesting

1. Solaris

application compiled on solaris 10 throwing error when executed on solaris 9

I have compiled my application on Solaris 10 with following description SunOS ldg1 5.10 Generic_138888-03 sun4v sparc SUNW,Sun-Blade-T6320 The compiler is Sun C++ 5.9 SunOS_sparc Patch 124863-01 2007/07/25 But when installing the application on Solaris 9 SunOS odcarch02 5.9... (2 Replies)
Discussion started by: ash_bit2k2
2 Replies

2. Solaris

Unable to login using ssh,telnet onto my solaris machine with solaris 10 installed

Hi, I am unable to login into my terminal hosting Solaris 10 and get the below error message "Server refused to allocate pty ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory " Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies

3. Solaris

root disk mirroring in solaris volume manager for solaris 10

Need a procedure document to do "root disk mirroring in solaris volume manager for solaris 10". I hope some one will help me asap. I need to do it production environment. Let me know if you need any deatils on this. Thanks, Rama (1 Reply)
Discussion started by: ramareddi16
1 Replies

4. Solaris

Patching Procedure in Solaris 10 with sun cluster having Solaris zone

Hi Gurus I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow. Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently... (1 Reply)
Discussion started by: nick101
1 Replies
devfsadm(1M)                                              System Administration Commands                                              devfsadm(1M)

NAME
devfsadm, devfsadmd - administration command for /dev SYNOPSIS
/usr/sbin/devfsadm [-C] [-c device_class] [-i driver_name] [ -n] [-r root_dir] [-s] [-t table_file] [-v] /usr/lib/devfsadm/devfsadmd DESCRIPTION
devfsadm(1M) maintains the /dev namespace. It replaces the previous suite of devfs administration tools including drvconfig(1M), disks(1M), tapes(1M), ports(1M), audlinks(1M), and devlinks(1M). The default operation is to attempt to load every driver in the system and attach to all possible device instances. Next, devfsadm creates logical links to device nodes in /dev and /devices and loads the device policy. devfsadmd(1M) is the daemon version of devfsadm(1M). The daemon is started during system startup and is responsible for handling both reconfiguration boot processing and updating /dev and /devices in response to dynamic reconfiguration event notifications from the kernel. For compatibility purposes, drvconfig(1M), disks(1M), tapes(1M), ports(1M), audlinks(1M), and devlinks(1M) are implemented as links to devfsadm. In addition to managing /dev, devfsadm also maintains the path_to_inst(4) database. OPTIONS
The following options are supported: -C Cleanup mode. Prompt devfsadm to cleanup dangling /dev links that are not normally removed. If the -c option is also used, devfsadm only cleans up for the listed devices' classes. -c device_class Restrict operations to devices of class device_class. Solaris defines the following values for device_class: disk, tape, port, audio, and pseudo. This option might be specified more than once to specify multiple device classes. -i driver_name Configure only the devices for the named driver, driver_name. -n Do not attempt to load drivers or add new nodes to the kernel device tree. -s Suppress any changes to /dev. This is useful with the -v option for debugging. -t table_file Read an alternate devlink.tab file. devfsadm normally reads /etc/devlink.tab. -r root_dir Presume that the /dev directory trees are found under root_dir, not directly under root (/). No other use or assumptions are made about root_dir. -v Print changes to /dev in verbose mode. EXIT STATUS
The following exit values are returned: 0 Successful completion. 1 An error occurred. FILES
/devices device nodes directory /dev logical symbolic links to /devices /usr/lib/devfsadm/devfsadmd devfsadm daemon /dev/.devfsadm_dev.lock update lock file /dev/.devfsadm_daemon.lock daemon lock file /etc/security/device_policy device policy file /etc/security/extra_privs additional device privileges ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
svcs(1), add_drv(1M), modinfo(1M), modload(1M), modunload(1M), rem_drv(1M), svcadm(1M), tapes(1M), path_to_inst(4), attributes(5), privi- leges(5), smf(5), devfs(7FS) NOTES
This document does not constitute an API. The /devices directory might not exist or might have different contents or interpretations in a future release. The existence of this notice does not imply that any other documentation that lacks this notice constitutes an API. devfsadm no longer manages the /devices name space. See devfs(7FS). The device configuration service is managed by the service management facility, smf(5), under the service identifier: svc:/system/device/local:default Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser- vice's status can be queried using the svcs(1) command. SunOS 5.10 6 Aug 2004 devfsadm(1M)
All times are GMT -4. The time now is 03:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy