12-14-2019
It was stated in post#1 that the OS is Solaris 9, and we all know it's outdated.
Later it was stated that it is not hooked to the Internet, so there is no direct threat.
It is pointless to further ride that dead horse.
There is equal config for 3 input devices and only one gets wrong. If the fault would be on the Solaris box then all 3 would be wrong - but it's one.
I keep saying this one input device is wrong.
If there is no alert on other systems then it's perhaps because their ntpd/chronyd is more fault tolerant.
9 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Hi Friends,
How can I Restore the Files present under "lost+found" Directory of a FileSystem (in Solaris & Tru64 OS) to their original Locations.
Now-a-days I am loosing lots of files in 2 of my Machines,
One running Solaris8 and other Tru64(Digital) Unix.
Thanx in... (1 Reply)
Discussion started by: dhasarath
1 Replies
2. UNIX for Dummies Questions & Answers
Is there some way to force the NTP server on a brand-new install to be "suitable" to sync other servers from? (I'm more concerned with synchronization between machines, and less concerned with what the actual time they sync to is)
For example, whenever I install fresh from the Fedora DVDs and... (0 Replies)
Discussion started by: jjinno
0 Replies
3. Linux
does anyone know how to change the treshold of 128ms in NTP.
in order to ignore these alarms:
Oct 27 14:44:15 rt1 ntpd: synchronisation lost
Oct 27 15:08:25 rt1 ntpd: time reset 0.688591 s
Oct 27 15:08:25 rt1 ntpd: synchronisation lost
Oct 27 15:28:45 rt1 ntpd: time reset 0.462257 s (0 Replies)
Discussion started by: modcan
0 Replies
4. UNIX for Advanced & Expert Users
Hi,
I was trying to call "script <an ip add>" command from .profile file to log everything whenever anyone logs in to this user. I did the following at the end of .profile. 1) Extracted the IP address who logged in 2) Called script < ip add> . The problem I am facing is all, aliases etc. written... (3 Replies)
Discussion started by: amicon007
3 Replies
5. AIX
Hi,
This is odd, however here goes. There are several shell scripts that run in our production environment AIX 595 LPAR m/c, which has sufficient memory 14GB (physical memory) and horsepower 5CPUs. However from time to time we get the following errors in these shell scripts. The time when these... (11 Replies)
Discussion started by: jerardfjay
11 Replies
6. Shell Programming and Scripting
Hi,
I have line in input file as below:
3G_CENTRAL;INDONESIA_(M)_TELKOMSEL;SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL
My expected output for line in the file must be :
"1-Radon1-cMOC_deg"|"LDIndex"|"3G_CENTRAL|INDONESIA_(M)_TELKOMSEL"|LAST|"SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL"
Can someone... (7 Replies)
Discussion started by: shis100
7 Replies
7. Solaris
Need to find a way to import an LP printers.conf file to CUPS. I have some new Solaris 11.1 boxes that need to have 300 printers added. (0 Replies)
Discussion started by: os2mac
0 Replies
8. UNIX for Dummies Questions & Answers
Hi All,
I'm completely new to bash scripting and still learning my way through albeit vey slowly.
I need to know where to insert my server names', my ip address numbers through out the script alas to no avail.
I'm also searching on how to save .sh (bash shell) script properly.... (25 Replies)
Discussion started by: profileuser
25 Replies
9. Shell Programming and Scripting
Hello.
System : opensuse leap 42.3
I have a bash script that build a text file.
I would like the last command doing :
print_cmd -o page-left=43 -o page-right=22 -o page-top=28 -o page-bottom=43 -o font=LatinModernMono12:regular:9 some_file.txt
where :
print_cmd ::= some printing... (1 Reply)
Discussion started by: jcdole
1 Replies
LEARN ABOUT SUNOS
ddi_get_devstate
ddi_get_devstate(9F) Kernel Functions for Drivers ddi_get_devstate(9F)
NAME
ddi_get_devstate - Check device state
SYNOPSIS
#include <sys/ddi.h>
#include <sys/sunddi.h>
ddi_devstate_t ddi_get_devstate(dev_info_t *dip);
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI)
PARAMETERS
dip Pointer to the device's dev_info structure
DESCRIPTION
The ddi_get_devstate() function returns a value indicating the state of the device specified by dip, as derived from the configuration
operations that have been performed on it (or on the bus on which it resides) and any fault reports relating to it.
RETURN VALUES
DDI_DEVSTATE_OFFLINE
The device is offline. In this state, the device driver is not attached, nor will it be attached automatically. The device cannot be
used until it is brought online.
DDI_DEVSTATE_DOWN
The device is online but unusable due to a fault.
DDI_DEVSTATE_QUIESCED
The bus on which the device resides has been quiesced. This is not a fault, but no operations on the device should be performed while
the bus remains quiesced.
DDI_DEVSTATE_DEGRADED
The device is online but only able to provide a partial or degraded service, due to a fault.
DDI_DEVSTATE_UP
The device is online and fully operational.
CONTEXT
The ddi_get_devstate() function may be called from user, kernel, or interrupt context.
NOTES
A device driver should call this function to check its own state at each major entry point, and before committing resources to a requested
operation. If a driver discovers that its device is already down, it should perform required cleanup actions and return as soon as possi-
ble. If appropriate, it should return an error to its caller, indicating that the device has failed (for example, a driver's read(9E) rou-
tine would return EIO).
Depending on the driver, some non-I/O operations (for example, calls to the driver's ioctl(9E) routine) may still succeed; only functions
which would require fully accessible and operational hardware will necessarily fail. If the bus on which the device resides is quiesced,
the driver may return a value indicating the operation should be retried later (for example, EAGAIN). Alternatively, for some classes of
device, it may be appropriate for the driver to enqueue the operation and service it once the bus has been unquiesced. Note that not all
busses support the quiesce/unquiesce operations, so this value may never be seen by some drivers.
SEE ALSO
attach(9E), ioctl(9E), open(9E), read(9E), strategy(9E), write(9E), ddi_dev_report_fault(9F)
SunOS 5.10 13 August 1999 ddi_get_devstate(9F)