01-13-2010
Can you kill ntpdate and xntpd daemons ?
10 More Discussions You Might Find Interesting
1. Windows & DOS: Issues & Discussions
All,
I have a Windows XP client which I need to get time synchronized from a Linux ntp server. What are the commands to perform the setup and configuration?
Thanks,
Mike (1 Reply)
Discussion started by: bubba112557
1 Replies
2. Solaris
All,
How do you set a Solaris 9 server which received ntp updates from a ntp server to broadcast them on a local subnet. I have created a /etc/inet/ntp.conf file to receive the updates from a server on network and need to make this server become like a ntp relay from the main server.
Any... (1 Reply)
Discussion started by: bubba112557
1 Replies
3. Solaris
Hi,
Can someone let me know the detail procedure for configuring NTP in Solaris/Windows/Linux environment....???
I would like to use any NTP Server on Windows Server & rest of the systems running with Solaris 10/9 & Linux be as NTP Client. All NTP Client should take the time from NTP Server... (8 Replies)
Discussion started by: jumadhiya
8 Replies
4. Fedora
Hello All
I have a problem about ntp, I am install a ntp server on a fedora 11 machine and I have 8 ntp client (solaris 10) everything working fine but just a server can not sync time . I have receive this error message
-bash-3.00# ntptime
ntp_gettime() returns code 5 (ERROR)
time... (1 Reply)
Discussion started by: bogacd
1 Replies
5. AIX
Hello everybody! When I run command "ntpdate" the following error occures
"ksh: ntpdate: 0403-006 Execute permission denied.
"
# oslevel -s
5300-08-06-0918
oslevel -r
5300-08
eny suggestion friends? :-) (3 Replies)
Discussion started by: wwwzviadi
3 Replies
6. AIX
Dears all
is it possible to have two NTP servers in one host ?
how i can configure them .
please advice (5 Replies)
Discussion started by: thecobra151
5 Replies
7. Solaris
How to add offset to NTP client so that, for eg., clock is -20 seconds? (2 Replies)
Discussion started by: orange47
2 Replies
8. Linux
i want to configure machine1 as ntp server. this machine has oel 5.9 64 bit installed and this machine is not connected to internet neither there is any ntp server.
there is another machine2 and i want to configure that as ntp client.
plz do tell me that what lines do i add in /etc/ntp.conf... (0 Replies)
Discussion started by: rehantayyab82
0 Replies
9. Ubuntu
Hello,
I am new to ubuntu Server OS and so trying to setup and ntp service on couple of servers.
I see ntp rpm is not installed.
# dpkg --get-selections | grep -v deinstall | grep ntp
ntpdate install
#
so I tried to installed ntp rpm using... (5 Replies)
Discussion started by: bobby320
5 Replies
10. Red Hat
Hi,
I have two ntp servers in my cluster and I want all the nodes in my cluster to sync with either of the ntp servers or just one. Unfortunately it keep rotating the sync, between my ntp server 1, ntp server 2 and local. Is there anyway I can change the sync to avoid local?
# ntpq -p
... (3 Replies)
Discussion started by: pjeedu2247
3 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)