10-01-2010
I think that you're probably right - it might very well be a start order issue.
To change the order, since you're running RH, edit the start scripts for named and ntpd in /etc/init.d and find the line:
# chkconfig: -
The two numbers after that are the numbers that control the start, and the stop, respectively.
For example, if it's "13 87" for named, you will be able to see that there's a symlink in /etc/rc3.d called S13named (and in all the other run levels that named is configured to start in) and also one called K87named in /etc/rc6.d (and the runlevels that named is configured to be stopped at).
Edit the first number to increase the number to start named and ntpd after the bond. Increase the second number to have those processes shut down before the bond.
Then you can use "chkconfig --del named" and "chkconfig --del ntpd" to remove the existing symlinks, and then "chkconfig --add named" and "chkconfig --add ntpd" to add them with the new orders.
10 More Discussions You Might Find Interesting
1. HP-UX
Hi,
I have a problem using NTP.
We have a setup as following :
client --> HP Server(NTP) --> DMZ server --> DMZ server --> Internet
Only some clients and our HP server is using NTP, the others are using different software.
Now I get an error every day :
Oct 1 13:17:15 nlunx1n1 xntpd:... (4 Replies)
Discussion started by: davidg
4 Replies
2. Solaris
Dear All
I'm solaris user . I need to setup NTP authentication for my office server but I have some question for ntp setting up. I need to know if i set authen NTP the client that doesn't set for authen key can sync time from authen ntp server or not ?? when i setup the authen at ntp server ... (1 Reply)
Discussion started by: goasutlor
1 Replies
3. UNIX for Dummies Questions & Answers
All -
i tried to sysn the clock from our server to get the timing and the server IP has been added in the ntp.conf file and i have some problems here. if some1 help me to solve this problem.
1. i can ping server
2. i was unable to ntpq -p (time out, no response from remote server, it looks... (2 Replies)
Discussion started by: March_2007
2 Replies
4. 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
5. Red Hat
Hi,
I have 4 machines and all are NTP configured with same ntp.conf file. But 3 machines are in sync with Time server and 4th machine is not contacting & sync with the NTP server. Please see the below details.
# service ntpd stop
Stopping ntpd: ... (0 Replies)
Discussion started by: uday123
0 Replies
6. Solaris
Hi,
I have edited the /etc/inet/ntp.conf file to point to a new time server. When I restart ntp on Solaris 10 using 'svcadm disable/enable ntp' it still points to the old ntp server when I run a 'ntpq -p'.
Any ideas?
Thanks.
Sparcman (4 Replies)
Discussion started by: sparcman
4 Replies
7. UNIX for Advanced & Expert Users
Hello every one i want to setup a ntp on sco unix 5.0.6 and i don't have any time server how can i do this with local time (1 Reply)
Discussion started by: kaydream
1 Replies
8. HP-UX
Hi
I wonder if its possible to setup NTP clients running HP-UX o.s. from a solaris 10 NTP server?
FR (3 Replies)
Discussion started by: fretagi
3 Replies
9. AIX
I got an ntp time problem on AIX server.
os version is AIX7.1
OS LEVEL 7.1.0.0
i got below output,when i run the below command
bash-3.2# ntpdate -dv XXXXXXXXXXXXXXXXXXXXXXXX
4 Dec 12:50:49 ntpdate: 3.4y
transmit(xxxxxxxxx)
receive(xxxxxxxxx)
transmit(xxxxxxxx)
receive(xxxxxxxxx)... (9 Replies)
Discussion started by: murali969
9 Replies
10. UNIX for Beginners Questions & Answers
Someone, please help on this issue:-
Note : for security reason i didn't mention hostnames and ips.
==============================================================================
# ntpstat
unsynchronised
polling server every 1024 s
Ntpstat showing unsynchronised.
... (29 Replies)
Discussion started by: shanmugaraj
29 Replies
LEARN ABOUT DEBIAN
shorewall-exclusion
SHOREWALL-EXCLUSION(5) [FIXME: manual] SHOREWALL-EXCLUSION(5)
NAME
exclusion - Exclude a set of hosts from a definition in a shorewall configuration file.
SYNOPSIS
!address-or-range[,address-or-range]...
!zone-name[,zone-name]...
DESCRIPTION
The first form of exclusion is used when you wish to exclude one or more addresses from a definition. An exclaimation point is followed by
a comma-separated list of addresses. The addresses may be single host addresses (e.g., 192.168.1.4) or they may be network addresses in
CIDR format (e.g., 192.168.1.0/24). If your kernel and iptables include iprange support, you may also specify ranges of ip addresses of the
form lowaddress-highaddress
No embedded whitespace is allowed.
Exclusion can appear after a list of addresses and/or address ranges. In that case, the final list of address is formed by taking the first
list and then removing the addresses defined in the exclusion.
Beginning in Shorewall 4.4.13, the second form of exclusion is allowed after all and any in the SOURCE and DEST columns of
/etc/shorewall/rules. It allows you to omit arbitrary zones from the list generated by those key words.
Warning
If you omit a sub-zone and there is an explicit or explicit CONTINUE policy, a connection to/from that zone can still be matched by the
rule generated for a parent zone.
For example:
/etc/shorewall/zones:
#ZONE TYPE
z1 ip
z2:z1 ip
...
/etc/shorewall/policy:
#SOURCE DEST POLICY
z1 net CONTINUE
z2 net REJECT
/etc/shorewall/rules:
#ACTION SOURCE DEST PROTO DEST
# PORT(S)
ACCEPT all!z2 net tcp 22
In this case, SSH connections from z2 to net will be accepted by the generated z1 to net ACCEPT rule.
In most contexts, ipset names can be used as an address-or-range. Beginning with Shorewall 4.4.14, ipset lists enclosed in +[...] may also
be included (see shorewall-ipsets[1] (5)). The semantics of these lists when used in an exclusion are as follows:
o !+[set1,set2,...setN] produces a packet match if the packet does not match at least one of the sets. In other words, it is like NOT
match set1 OR NOT match set2 ... OR NOT match setN.
o +[!set1,!set2,...!setN] produces a packet match if the packet does not match any of the sets. In other words, it is like NOT match set1
AND NOT match set2 ... AND NOT match setN.
EXAMPLES
Example 1 - All IPv4 addresses except 192.168.3.4
!192.168.3.4
Example 2 - All IPv4 addresses except the network 192.168.1.0/24 and the host 10.2.3.4
!192.168.1.0/24,10.1.3.4
Example 3 - All IPv4 addresses except the range 192.168.1.3-192.168.1.12 and the network 10.0.0.0/8
!192.168.1.3-192.168.1.12,10.0.0.0/8
Example 4 - The network 192.168.1.0/24 except hosts 192.168.1.3 and 192.168.1.9
192.168.1.0/24!192.168.1.3,192.168.1.9
Example 5 - All parent zones except loc
any!loc
FILES
/etc/shorewall/hosts
/etc/shorewall/masq
/etc/shorewall/rules
/etc/shorewall/tcrules
SEE ALSO
shorewall(8), shorewall-accounting(5), shorewall-actions(5), shorewall-blacklist(5), shorewall-hosts(5), shorewall_interfaces(5),
shorewall-ipsets(5), shorewall-maclist(5), shorewall-masq(5), shorewall-nat(5), shorewall-netmap(5), shorewall-params(5),
shorewall-policy(5), shorewall-providers(5), shorewall-proxyarp(5), shorewall-rtrules(5), shorewall-routestopped(5), shorewall-rules(5),
shorewall.conf(5), shorewall-secmarks(5), shorewall-tcclasses(5), shorewall-tcdevices(5), shorewall-tcrules(5), shorewall-tos(5),
shorewall-tunnels(5), shorewall-zones(5)
NOTES
1. shorewall-ipsets
http://www.shorewall.net/manpages/shorewall-ipsets.html
[FIXME: source] 06/28/2012 SHOREWALL-EXCLUSION(5)