07-06-2012
Hi All,
In addition to above details,
The RHEL server is running on the Dell Blade, and have storage allocated from 1. Equillogic, and MD3200.
10 More Discussions You Might Find Interesting
1. Red Hat
Hi Gurus
I am trying to install RHEL linux enterprise Edition v5 on a Dell Optiplex 320 desktop.
After the Grub menu,i get the error,Kernel could not be loaded.
I am a newbie in linux and would appreciate any help in moving forward.
Thanks
HG (1 Reply)
Discussion started by: Hari_Ganesh
1 Replies
2. Red Hat
Hi,
My Linux VMs are running on citrix XEN.Somehow the time drift is too high (going very fast). Even if the correct time configured using date -s command, for every 1 hr it is differing almost 5 - 10 mins.
Tried configuring ntpd (local NTP server) and still it is not synchronized.
Machine... (2 Replies)
Discussion started by: uday123
2 Replies
3. UNIX for Dummies Questions & Answers
how to change ethernet cable of iscsi initiator (iscsi client) (0 Replies)
Discussion started by: pankajd
0 Replies
4. Red Hat
Hi,
I heard a command that can collect all RHEL 5 log in a single compress file before I forget.
Does any body know...What the command is ?
Thanks. (4 Replies)
Discussion started by: nnnnnnine
4 Replies
5. Red Hat
Hi all,
Im studying rhcsa as of now, so yum installation and dependencies are messing me to not workit out.
i have dual os, win 7 & rhel 6.
i have tried this installation of vsftpd package with rhel 6 dvd in VM rhel 6 in win 7 as well as host rhel 6.still the same issue.
below error... (6 Replies)
Discussion started by: redhatlbug
6 Replies
6. Red Hat
Hi,
I have a requirement to compress logs that generate daily. Below is the logrotate configuration for this
But for some kind of reason the logs are not getting compressed daily. When tried to execute the logrotate manually with -d it says "log does not need rotating."
The path... (0 Replies)
Discussion started by: EmbedUX
0 Replies
7. Linux
HI All
I am facing issue in installation of Red Hat 6.5 on SAN.. i am having a partion of 2 TB in my SAN and i am installing the operating system after completed the installation it not booting and giving the error. (2 Replies)
Discussion started by: deviltech
2 Replies
8. Red Hat
Friends,
I have 8CPU/24gb RAM in my Linux servers around 30+. All the servers are running with Java based application with NFS mounted.
The problem what I have is, When I reboot servers the server memory looks decent. But after some time the "cached" memory increasing and "free" memory... (5 Replies)
Discussion started by: baluchen
5 Replies
9. Shell Programming and Scripting
Greetings Experts,
We are migrating from AIX to RHEL Linux. I have created a script to verify and report the NULLs and SPACEs in the key columns and duplicates on key combination of "|" delimited set of big files. Following is the code that was successfully running in AIX.
awk -F "|" 'BEGIN {... (5 Replies)
Discussion started by: chill3chee
5 Replies
10. UNIX for Advanced & Expert Users
Hello folks,
I am facing a weird issue on one of the red hat linux 5 box. There is an oracle id which i want to change the primary group. Currently the primary group id is 16600, I did changed it to 16601 using below command:
usermod -g 16601 oracle
But it did not changed. I have tried... (3 Replies)
Discussion started by: snchaudhari2
3 Replies
LEARN ABOUT FREEBSD
iscsi
ISCSI(4) BSD Kernel Interfaces Manual ISCSI(4)
NAME
iscsi -- iSCSI initiator
SYNOPSIS
To compile this driver into the kernel, place the following line in the kernel configuration file:
device iscsi
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
iscsi_load="YES"
DESCRIPTION
The iscsi subsystem provides the kernel component of an iSCSI initiator. The initiator is the iSCSI client, which connects to an iSCSI tar-
get, providing local access to a remote block device. The userland component is provided by iscsid(8) and both the kernel and userland are
configured using iscsictl(8). The iscsi subsystem is responsible for implementing the "Full Feature Phase" of the iSCSI protocol.
SYSCTL VARIABLES
The following variables are available as both sysctl(8) variables and loader(8) tunables:
kern.iscsi.ping_timeout
The number of seconds to wait for the target to respond to a NOP-Out PDU. In the event that there is no response within that time
the session gets forcibly restarted.
kern.iscsi.iscsid_timeout
The number of seconds to wait for ctld(8) to establish a session. After that time iscsi will abort and retry.
kern.iscsi.login_timeout
The number of seconds to wait for a login attempt to succeed. After that time iscsi will abort and retry.
kern.iscsi.maxtags
The maximum number of outstanding IO requests.
kern.iscsi.fail_on_disconnection
Controls the behavior after an iSCSI connection has been dropped due to network problems. When set to 1, a dropped connection causes
the iSCSI device nodes to be destroyed. After reconnecting, they will be created again. By default, the device nodes are left
intact. While the connection is down all input/output operations are suspended, to be retried after the connection is reestablished.
SEE ALSO
iscsi.conf(5), iscsictl(8), iscsid(8)
HISTORY
The iscsi subsystem first appeared in FreeBSD 10.0.
AUTHORS
The iscsi subsystem was developed by Edward Tomasz Napierala <trasz@FreeBSD.org> under sponsorship from the FreeBSD Foundation.
BSD
September 11, 2014 BSD