Hi ,
My Sun Machine Rebooted by itself 2 days back . Its running fine now , But i wanted to find out wat caused it to reboot...
This is wat the var/adm/messages show .
Kern.notice:- System booting after fatal error FATAL...
Wat causes this message ...
And wat tasks should i do to ensure it... (6 Replies)
Hi All,
Since server is located at remote place so how to identify which user rebooted the server. Is there any way to identify the user.
Thanks in advance,
Reg,
Bache Gowda (1 Reply)
hi
anyone one here for helping me? plzzzzzzzzzzzzz
I would like to know how Licensing information such as the operating system revision level and license restrictions in terms of user numbers can be seen?
and When was the system last rebooted can also be seen? (3 Replies)
dear all
Iam unix administrator and yesterday the server rebooted alone and when i check the messages i find the below errors can you help me (3 Replies)
Hi,
I want to know how to find out which user has rebooted the server? I have used last command but it is not giving username though it is showing below output
reboot --------------- date
Regards,
Manoj (5 Replies)
Hi,
Not sure if this was asked in a tread already(searched but did not find anything :( )
I want to know who rebooted a system without reading through allot of /var/adm/messages
I know the command last will show me when the system was rebooted
*user* *Login Protocol* *IP address* ... (2 Replies)
Hi Team,
server rebooted happen sunddely, i check all the log files but ..i didn't find any reason...kindly share your's ideas with me...
Thanks in advace
Rajesh_Apple...:b: (1 Reply)
Hi,
Yesterday one of Red Hat Server 4.2 got rebooted.
I have checked /var/log/messages, but does not find out any serious issue related to peformance / hardware issue.
how to find out why server was rebooted? (1 Reply)
Discussion started by: manoj.solaris
1 Replies
LEARN ABOUT SUNOS
ntp.keys
ntp.keys(5) File Formats ntp.keys(5)NAME
ntp.keys - NTP symmetric key file format configuration file
SYNOPSIS
[--option-name] [--option-name value]
All arguments must be options.
DESCRIPTION
This document describes the format of an NTP symmetric key file. For a description of the use of this type of file, see the "Authentica-
tion Support" section of the ntp.conf(5) page.
ntpd(8) reads its keys from a file specified using the -k command line option or the keys statement in the configuration file. While key
number 0 is fixed by the NTP standard (as 56 zero bits) and may not be changed, one or more keys numbered between 1 and 65535 may be arbi-
trarily set in the keys file.
The key file uses the same comment conventions as the configuration file. Key entries use a fixed format of the form
keyno type key opt_IP_list
where keyno is a positive integer (between 1 and 65535), type is the message digest algorithm, key is the key itself, and opt_IP_list is an
optional comma-separated list of IPs where the keyno should be trusted. that are allowed to serve time. Each IP in opt_IP_list may con-
tain an optional /subnetbits specification which identifies the number of bits for the desired subnet of trust. If opt_IP_list is empty,
any properly-authenticated message will be accepted.
The key may be given in a format controlled by the type field. The type MD5 is always supported. If ntpd was built with the OpenSSL
library then any digest library supported by that library may be specified. However, if compliance with FIPS 140-2 is required the type
must be either SHA or SHA1.
What follows are some key types, and corresponding formats:
MD5 The key is 1 to 16 printable characters terminated by an EOL, whitespace, or a # (which is the "start of comment" character).
SHA
SHA1
RMD160 The key is a hex-encoded ASCII string of 40 characters, which is truncated as necessary.
Note that the keys used by the ntpq(8) and ntpdc(8) programs are checked against passwords requested by the programs and entered by hand,
so it is generally appropriate to specify these keys in ASCII format.
FILES
/etc/ntp.keys the default name of the configuration file
SEE ALSO ntp.conf(5), ntpd(1), ntpdate(1), ntpdc(1), sntp(1)AUTHORS
The University of Delaware and Network Time Foundation
COPYRIGHT
Copyright (C) 1992-2017 The University of Delaware and Network Time Foundation all rights reserved. This program is released under the
terms of the NTP license, <http://ntp.org/license>.
BUGS
Please send bug reports to: http://bugs.ntp.org, bugs@ntp.org
NOTES
This document was derived from FreeBSD.
This manual page was AutoGen-erated from the ntp.keys option definitions.
4.2.8p13 20 Feb 2019 ntp.keys(5)