9 More Discussions You Might Find Interesting
1. Linux
When unlocking a Linux server's console there's no event indicating successful logging
Is there a way I can fix this ?
I have the following in my rsyslog.conf
auth.info /var/log/secure
authpriv.info /var/log/secure (1 Reply)
Discussion started by: walterthered
1 Replies
2. Web Development
A Gbytes long log
/var/log/apache2/access_log
causes my question: How to stop my IP logging (just because of frequent AJAX/setTimeout).
As config:
SetEnvIf Remote_Addr "ip\.ip\.ip\.ip" dontlog
CustomLog /var/log/apache2/access_log common env=!dontlog
In
/etc/apache2/httpd.conf ... (0 Replies)
Discussion started by: Xcislav
0 Replies
3. HP-UX
Hi All,
I've tried starting syslogd on our hp-ux 11.31 server. However, it is not getting started nor it is updating the syslog file.
There is no space issue also. However, the mail.log file is approx 2GB, can that be of any issue. Please find the details below:
# /sbin/init.d/syslogd... (2 Replies)
Discussion started by: Kits
2 Replies
4. UNIX for Dummies Questions & Answers
How to stop the uprintfd daemon? After uncommenting, kill -9 doesn't work on the process either.
EDIT: Nevermind. I've got this now.
Cheers,
DH (2 Replies)
Discussion started by: Devyn
2 Replies
5. UNIX for Dummies Questions & Answers
Hi,
my question is probably quite easy. On one linux machine I have messages being constantly being written to /var/log/messages. An ntpd message comes in every few seconds. I can see new ones with tail messages. On the other machine there seems to be no messages arriving in /var/log/messages.... (3 Replies)
Discussion started by: jackiebaron
3 Replies
6. Shell Programming and Scripting
Hi guys if for every command you issued successfully where to be logged from a script and them sent an email to the admistrator how could i stop that so that i wouldnt have to delete admin mail all the time. I would only want to produce output if there was an error. (5 Replies)
Discussion started by: musicmancanora
5 Replies
7. UNIX for Advanced & Expert Users
How can I tell my syslog.conf to log "syslog start/stop/restart" messages on a Solaris box? (1 Reply)
Discussion started by: SunnyK
1 Replies
8. Solaris
Hello
One of our applications initiates an ftp logon to itself twice every second ...(to check some files or something im not sure) but every time it does this it logs an entry into the wtmpx database, this file is now getting absolutely huge and whilst I know that I could implement some type of... (1 Reply)
Discussion started by: hcclnoodles
1 Replies
9. UNIX for Dummies Questions & Answers
Hello,
I need a few information/explanation about system messages, syslog.conf file and syslogd daemon.
My problem is the following: I would like to log all system messages related to hardware problems into a particular file. For that, i have to add an entry in the syslog.conf file.
I know... (1 Reply)
Discussion started by: VeroL
1 Replies
TIMED(8) BSD System Manager's Manual TIMED(8)
NAME
timed -- time server daemon
SYNOPSIS
timed [-dMt] [-F host ...] [-G netgroup] [-i network | -n network]
DESCRIPTION
The timed utility is a time server daemon which is normally invoked at boot time from the rc(8) file. It synchronizes the host's time with
the time of other machines, which are also running timed, in a local area network. These time servers will slow down the clocks of some
machines and speed up the clocks of others to bring them to the average network time. The average network time is computed from measurements
of clock differences using the ICMP timestamp request message.
The following options are available:
-d Enable debugging mode; do not detach from the terminal.
-F host ...
Create a list of trusted hosts. The timed utility will only accept trusted hosts as masters. If it finds an untrusted host claiming
to be master, timed will suppress incoming messages from that host and call for a new election. This option implies the -M option.
If this option is not specified, all hosts on the connected networks are treated as trustworthy.
-G netgroup
Specify a netgroup of trustworthy hosts, in addition to any masters specified with the -M flag. This option may only be specified
once.
-i network
Add network to the list of networks to ignore. All other networks to which the machine is directly connected are used by timed.
This option may be specified multiple times to add more than one network to the list.
-M Allow this host to become a timed master if necessary.
-n network
Add network to the list of allowed networks. All other networks to which the machine is directly connected are ignored by timed.
This option may be specified multiple times to add more than one network to the list.
-t Enable tracing of received messages and log to the file /var/log/timed.log. Tracing can be turned on or off while timed is running
with the timedc(8) utility.
The -n and -i flags are mutually exclusive and require as arguments real networks to which the host is connected (see networks(5)). If nei-
ther flag is specified, timed will listen on all connected networks.
A timed running without the -M nor -F flags will always remain a slave. If the -F flag is not used, timed will treat all machines as trust-
worthy.
The timed utility is based on a master-slave scheme. When timed is started on a machine, it asks the master for the network time and sets
the host's clock to that time. After that, it accepts synchronization messages periodically sent by the master and calls adjtime(2) to per-
form the needed corrections on the host's clock.
It also communicates with date(1) in order to set the date globally, and with timedc(8), a timed control utility. If the machine running the
master becomes unreachable, the slaves will elect a new master from among those slaves which are running with at least one of the -M and -F
flags.
At startup timed normally checks for a master time server on each network to which it is connected, except as modified by the -n and -i
options described above. It will request synchronization service from the first master server located. If permitted by the -M or -F flags,
it will provide synchronization service on any attached networks on which no trusted master server was detected. Such a server propagates
the time computed by the top-level master. The timed utility will periodically check for the presence of a master on those networks for
which it is operating as a slave. If it finds that there are no trusted masters on a network, it will begin the election process on that
network.
One way to synchronize a group of machines is to use ntpd(8) to synchronize the clock of one machine to a distant standard or a radio
receiver and -F hostname to tell its timed to trust only itself.
Messages printed by the kernel on the system console occur with interrupts disabled. This means that the clock stops while they are print-
ing. A machine with many disk or network hardware problems and consequent messages cannot keep good time by itself. Each message typically
causes the clock to lose a dozen milliseconds. A time daemon can correct the result.
Messages in the system log about machines that failed to respond usually indicate machines that crashed or were turned off. Complaints about
machines that failed to respond to initial time settings are often associated with ``multi-homed'' machines that looked for time masters on
more than one network and eventually chose to become a slave on the other network.
WARNINGS
Temporal chaos will result if two or more time daemons attempt to adjust the same clock. If both timed and another time daemon are run on
the same machine, ensure that the -F flag is used, so that timed never attempts to adjust the local clock.
The protocol is based on UDP/IP broadcasts. All machines within the range of a broadcast that are using the TSP protocol must cooperate.
There cannot be more than a single administrative domain using the -F flag among all machines reached by a broadcast packet. Failure to fol-
low this rule is usually indicated by complaints concerning ``untrusted'' machines in the system log.
FILES
/var/log/timed.log tracing file for timed
/var/log/timed.masterlog log file for master timed
SEE ALSO
date(1), adjtime(2), gettimeofday(2), icmp(4), netgroup(5), networks(5), ntpd(8), timedc(8)
R. Gusella and S. Zatti, TSP: The Time Synchronization Protocol for UNIX 4.3BSD.
HISTORY
The timed utility appeared in 4.3BSD.
BSD
May 11, 1993 BSD