Sponsored Content
Operating Systems AIX Determining how long device has been in defined state Post 302766219 by jwholey on Monday 4th of February 2013 11:51:14 AM
Old 02-04-2013
Determining how long device has been in defined state

All,

Hoping you can help. I'm wondering how I can determine how long a device (network interface) has been in a defined state. Know there's a way, just can't figure it out.

Thanks in advance!
 

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Hitting with custom port in CLOSE_WAIT state for long time in solaris 10

Hi, Occasionally I am getting the port state in CLOSE_WAIT for long time in the solaris server. I am not sure is it application problem or not. Because we are using port 9009 for Tomcat process in our web application, some time when I start the application, the port 9009 is in CLOSE_WAIT... (0 Replies)
Discussion started by: mgmk.84
0 Replies

2. AIX

Device Available / Define state

Hi, I would like to know wheather it is possible to make device in availabe state? if for same reason os is not able to make it in available state. and it is in define state. (2 Replies)
Discussion started by: manoj.solaris
2 Replies

3. Red Hat

Unable To Activate Ethernet Network Device in RHEL 5.5 - e100 device eth0 does not seem to be presen

Hi All, Could anyone please help to resolve the below problem. I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error. I spent 2 days for the above and go through with several suggestion found by googling. But no luck. ... (0 Replies)
Discussion started by: Tanmoy
0 Replies

4. AIX

Open firmware state to running state

Hi Admins, I am having a whole system lpar in open firmware state on HMC. How can I bring it to running state ? Let me know. Thanks. (2 Replies)
Discussion started by: snchaudhari2
2 Replies

5. HP-UX

Failed to open tape device /dev/rmt/0mn:Device busy (errno = 16)

Hi, Unable to make tape backup, please help. /opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00 * Creating local directories for configuration files and archive. ======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery. (Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
cfgmgr_get_state(9r)													      cfgmgr_get_state(9r)

NAME
cfgmgr_get_state - General: Determines the configuration state SYNOPSIS
int cfgmgr_get_state( char *driver_name, int *driver_cfg_state ); ARGUMENTS
Specifies the name of the device driver whose configuration state you want to obtain. This name is a string that matches the string you specified for the entry_name item in the /etc/sysconfigtab database. Typically, third-party driver writers specify the driver name (fol- lowed by a colon) in the sysconfigtab file fragment, which gets appended to the /etc/sysconfigtab database during the driver product installation. Returns one of the following state value bits to the driver_cfg_state argument: The specified device driver is in the dynamic configuration state. This means the driver was dynamically configured into the kernel. The specified device driver is in the static configuration state. This means the driver was statically configured into the kernel. DESCRIPTION
The cfgmgr_get_state routine obtains the configuration state of the specified device driver. The specified device driver is in either the static configuration state or the dynamic configuration state. The cfgmgr_get_state routine returns the state value in the driver_cfg_state argument. Driver writers should store this state value in an xx_is_dynamic variable or some similarly named variable. You typically call the cfgmgr_get_state routine in the CFG_OP_CONFIGURE entry point of the device driver's configure routine. RETURN VALUES
Upon successful completion, cfgmgr_get_state returns the value ESUCCESS. This success value indicates that cfgmgr_get_state returned the configuration state of the specified device driver in the driver_cfg_state argument. Otherwise, cfgmgr_get_state returns one of the follow- ing error constants defined in /usr/sys/include/sys/sysconfig.h and /usr/sys/include/sys/errno.h: The device driver that you specified in the driver_name argument does not exist. In this case, cfgmgr_get_state cannot return the configuration state of the specified device driver in the driver_cfg_state argument. The device driver that you specified in the driver_name argument is not a valid name. EXAMPLES
See Writing Device Drivers: Tutorial for a code example of the cfgmgr_get_state interface. SEE ALSO
Routines: cfgmgr_set_status(9r) cfgmgr_get_state(9r)
All times are GMT -4. The time now is 06:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy