I have a list of LUN ID, my task is to find if disk has been added or not. How do I do that? I have been searching the forum and not able to find answer.
thanks (4 Replies)
Good day!
I’m a beginner HP-UX administrator. I have a task to create mulitipassing (I can mistake in this word) to new 3 disks which connected to my server from EVA. It is my first task to work with Secure Path. I have read what command I need to execute, but I don’t know, how to get the WWNN... (2 Replies)
hi all,
i have added new LUN to Redhat 5. i have already scanned LUN devices and it is confirmed that Kernel sees the newly added LUN's. i have used /proc/partitions and verified that my disks are there.
However, i cannot find my disk using fdisk -l command. I am not sure what did i... (2 Replies)
Hi,
I am not getiting lun id information on VIO Server. I have used the command fget_config command.
just showing # prompt.
I would like know wheather any other command is there equiv of fget_config
which will display lun id? (4 Replies)
Dear all,
i want to get the LUN ID for some disks in solaris 10
what commands options for the MPXIO and inq i want these utilities only
because i don't have solution enabler or powerpath
BR, (1 Reply)
Hi,
I am having a text file with the following contents
###########
File1
###########
some
page1.txt
text
page.txt
When I sort this file on Red Hat 5, then I get the following output
###########
File1
###########
page1.txt
page.txt
some (3 Replies)
Dear community,
I'm in trouble with Red Hat Server 5.8. After rebooting the server, I loose two interfaces used for bond2 (eth4 and eth5). I reboot twice the server but the result is always:
# service network restart
Shutting down interface bond0:
Shutting down... (1 Reply)
Discussion started by: Lord Spectre
1 Replies
LEARN ABOUT X11R4
xinetd.log
XINETD.LOG(5) File Formats Manual XINETD.LOG(5)NAME
xinetd.log - xinetd service log format
DESCRIPTION
A service configuration may specify various degrees of logging when attempts are made to access the service. When logging for a service is
enabled, xinetd will generate one-line log entries which have the following format (all entries have a timestamp as a prefix):
entry: service-id data
The data depends on the entry. Possible entry types include:
START generated when a server is started
EXIT generated when a server exits
FAIL generated when it is not possible to start a server
USERID generated if the USERID log option is used.
NOID generated if the USERID log option is used, and the IDONLY service flag is used, and the remote end does not identify
who is trying to access the service.
In the following, the information enclosed in brackets appears if the appropriate log option is used.
A START entry has the format:
START: service-id [pid=%d] [from=%d.%d.%d.%d]
An EXIT entry has the format:
EXIT: service-id [type=%d] [pid=%d] [duration=%d(sec)]
type can be either status or signal. The number is either the exit status or the signal that caused process termination.
A FAIL entry has the format:
FAIL: service-id reason [from=%d.%d.%d.%d]
Possible reasons are:
fork a certain number of consecutive fork attempts failed (this number is a configurable parameter)
time the time check failed
address the address check failed
service_limit the allowed number of server instances for this service would be exceeded
process_limit a limit on the number of forked processes was specified and it would be exceeded
A DATA entry has the format:
DATA: service-id data
The data logged depends on the service.
login remote_user=%s local_user=%s tty=%s
exec remote_user=%s verify=status command=%s
Possible status values:
ok the password was correct
failed the password was incorrect
baduser no such user
shell remote_user=%s local_user=%s command=%s
finger received string or EMPTY-LINE
A USERID entry has the format:
USERID: service-id text
The text is the response of the identification daemon at the remote end excluding the port numbers (which are included in the response).
A NOID entry has the format:
NOID: service-id IP-address reason
SEE ALSO xinetd(1L), xinetd.conf(5)
28 April 1993 XINETD.LOG(5)