Determining how long device has been in defined state Post: 302766467

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

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.

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

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.

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

LEARN ABOUT DEBIAN

omninames

OMNINAMES(8)						      System Manager's Manual						      OMNINAMES(8)

NAME

       omniNames - OmniORB Interoperable Naming Service

SYNOPSIS

       omniNames [options] [omniORB-options]

DESCRIPTION

       This manual page documents briefly the omniNames command.

       omniNames  is omniORBs Interoperable Naming Service for CORBA, an implementation of the OMG's COS Naming Service Specification.	To make it
       easy to use omniNames with corbaname URIs, it starts with the default port of 2809 and an object key of NameService  for  the  root  naming
       context.

       When started for the first time omniNames needs to be told which port it should listen on.  This is specified with the -start option.  Sub-
       sequentley omniNames will always determine its port from the log file which it writes.

       When omniNames starts up successfully it writes the stringified object reference for its root context on standard error.

OPTIONS

       A summary of options is included below.	For a complete description, see the HTML pages included in the omniorb-doc package.

       -start [port]
	      This needs to be used the first time omniNames is run.  With no port argument the standard default of 2809 is used.

       -logdir directory_name
	      This specifies the directory where the log/data files are kept.  By default /var/lib/omniorb-nameserver/ is used.

       -errlog file_name
	      Where to redirect standard error output.

       -ignoreport
	      Ignore the port specification.

ENVIRONMENT

       OMNINAMES_LOGDIR
	      Alternate way to specify the directory where the log/data files are kept.

       OMNINAMES_ITBC
	      Idle time between checkpoints in seconds.  It defaults to 15 minutes.

SEE ALSO

       omniMapper(8).
       The programs are documented fully by the HTML documentation in the omniorb-doc package.

AUTHOR

       omniNames was written by Duncan Grisby <duncan@grisby.org>

       This manual page was written by Floris Bruynooghe <floris.bruynooghe@gmail.com>, for the Debian project (but may be used by others).

								    30 Apr 2007 						      OMNINAMES(8)