10-11-2001
Maybe your networking daemons aren't worknign properly. I'd run linuxconf and check to see if all of the services are running properly.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I was just wondering how to install Pioc onto FreeBSD?
could someone help mee? (1 Reply)
Discussion started by: Swifty
1 Replies
2. UNIX for Dummies Questions & Answers
Hello. it`s possible tha your are reading a messege from the
most recent unix user... mi.
My question is. can i install macromedia coldfusion in unix system? (1 Reply)
Discussion started by: waguilar
1 Replies
3. AIX
Hii everyone,
I am trying to install RHEL5 on system p Power 5-510 series box through installable CD's. Machine boots from CD and I receive boot prompt without any issue. After this when i press "Enter" tab, it starts loading Kernel and throws below error:-
Also LED code i am receiving is... (6 Replies)
Discussion started by: Shrek
6 Replies
4. UNIX for Dummies Questions & Answers
Hi everybody,
I have several computers that are configured to install when I plug them on the network. The hard drive come's empty, but I think they have a parameter in the BIOS that allow the machines to install from the network.
My problem is that in most cases, available bw is weak and... (5 Replies)
Discussion started by: chebarbudo
5 Replies
5. Linux
Hello to everyone,
I am new to linux and I want to move to this system after bad experiences with windows.
I have also a particular problem. An old laptop is probably able to handle just linux at this point of its life.
The cdrom is gone, the bios doesn't have usb boot support, there is no... (6 Replies)
Discussion started by: highkftj
6 Replies
6. Ubuntu
I want to install Ubuntu Ultimate 2.9. I downloaded ISO form its site and burnt it on DVD and tried to install it. But my DVD reader is not working properly so installation fails in between it. I have another OS as Windows.
Can any body tell that if I can install Ubuntu Ultimate directly from... (8 Replies)
Discussion started by: nixhead
8 Replies
7. UNIX for Advanced & Expert Users
Hi
On Linux systems there is a command called "column".
column - columnate lists
Synopsis
column -tx] -c columns] -s sep] file ...]
Description
The column utility formats its input into multiple columns. Rows are filled before columns. Input is taken from file operands, or,... (3 Replies)
Discussion started by: slashdotweenie
3 Replies
8. AIX
I have a following requirement in production
system 1 : LINUX
User: abcd
system 2: AIX (it is hosting a production DB)
Requirement
user abcd from system 1 should have read access on archive log files created by DB on system 2. The log files are created with permissions 540 by user ora ,... (2 Replies)
Discussion started by: amitnm1106
2 Replies
9. Programming
Hi all
What is the qualification required by Linux/Solaris System Administrator to become a Linux/Solaris System Programmer as to gain complete knowledge on computers.
Thanks (1 Reply)
Discussion started by: Tlogine
1 Replies
voliod(8) System Manager's Manual voliod(8)
NAME
voliod - Start, stop, and report on Logical Storage Manager kernel daemons
SYNOPSIS
/sbin/voliod
/sbin/voliod [-f] set count
OPTIONS
The following option is used by voliod: Force the kill of the last I/O daemon. Without this option, the I/O daemons can only be reduced to
one.
DESCRIPTION
The voliod utility starts, stops, or reports on Logical Storage Manager I/O daemons. An I/O daemon is a process that provides a process
context for processing any work that needs to be done to process Logical Storage Manager I/O.
When invoked with no arguments, voliod prints the current number of volume I/O daemons on the standard output.
When invoked with the set keyword, the number of daemons specified by count will be created. If more volume I/O daemons exist than are
specified by count, then the excess processes will be terminated. If more than the maximum number are created (currently 64), the requested
number will be silently truncated to that maximum.
The number of daemons to create for general I/O handling depends on system load and usage. One daemon for each CPU on the system is gener-
ally adequate, unless volume recovery seems unusually slow.
Each I/O daemon starts in the background and creates an asynchronously-running kernel thread and becomes a volume I/O daemon. The voliod
utility does not wait for these threads to complete.
NOTES
LSM automatically sets the number of I/O daemons when the system starts, so it is usually not necessary to set or change the number of I/O
daemons with this command.
LSM I/O daemons cannot be killed directly through the use of signals.
The number of Logical Storage Manager I/O daemons currently running can only be determined by running voliod; I/O daemons do not appear in
the list of processes produced by the ps(1) command.
EXIT CODES
The voliod utility prints a diagnostic on the standard error, and exits if an error is encountered. If an I/O error occurs within a spawned
I/O daemon thread, then the I/O is not reflected in the exit status for voliod. Otherwise, voliod returns a nonzero exit status on errors.
Usage errors result in an exit status of 1 and a usage message. If the requested number of daemons cannot be created, then the exit status
is 2, and the number of daemons that were successfully started is reported. If any other error occurs, the exit status is 3.
FILES
The device used to report on and start volume I/O daemon kernel threads.
SEE ALSO
fork(2), volintro(8), vold(8), voldctl(8) ,pthread(8)
voliod(8)