01-21-2014
Both systems reboot OK? Did you look in the older /var/adm/messages log files and not just the current messages file? Is crash dump enabled? If not, you should enable it if possible.
This User Gave Thanks to fpmurphy For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello
We had an old system designed in fortran that ran on a IBM RS6000 AIX 3.2 system. The person who designed is long gone. It was replaced with a completely different (non unix) system 6 years ago. We still used it for historical lookups of older information. Well yesterday it died. The... (5 Replies)
Discussion started by: billfaith
5 Replies
2. High Performance Computing
All-
I am new to these forums so please excuse me if this post is in the wrong place.
I had a node crash in a 4 node cluster and mgmt has determined this node will not be part of the cluster when rebuilt. I am researching how to remove it from the cluster information on the other 3 nodes and... (2 Replies)
Discussion started by: bluescreen
2 Replies
3. AIX
Is there such location or command to know how many times did you reboot your server in that particular day?in AIX. (3 Replies)
Discussion started by: kenshinhimura
3 Replies
4. Linux
Hi everybody,
I want to find out all the processes that ran before a server crashed. Is that possible?
I've looked in /var/log/messages and found out that the system was out of memory.
A user probably wrote a script (in Perl or Python) that used up all available memory and crashed the... (11 Replies)
Discussion started by: z1dane
11 Replies
5. Red Hat
What do you check????
Thanks!
JC (0 Replies)
Discussion started by: 300zxmuro
0 Replies
6. Shell Programming and Scripting
Hi, I need a sample of a script that will check a specific directory multiple times throughout the day, and scp the newest file to another server.
Example: current file is misc_file.txt_02272011 (the last part is the date), once that has been secure copied, another one may come in later the... (1 Reply)
Discussion started by: richasmi
1 Replies
7. Programming
Hello,
i'm trying to implement the times() function and i'm programming in C.
I'm using the "struct tms" structure which consists of the fields:
The tms_utime structure member is the CPU time charged for the execution of user instructions of the calling process.
The tms_stime structure... (1 Reply)
Discussion started by: g_p
1 Replies
8. IP Networking
If Freebsd DNS server that served 100 people is crashed. How to move this 100 people to a new FreeBSD DNS server as quickly as possible? (1 Reply)
Discussion started by: AIX_30
1 Replies
9. Solaris
Hi,
anyone please let us know how to write shell script to find the missing mountpoints after server reboot.
i want to take the mountpount information before server reboot, and validate the mountpoints after server reboot if any missing.please let us know the shell script from begining to end as... (24 Replies)
Discussion started by: VenkatReddy786
24 Replies
10. Shell Programming and Scripting
Hello all,
I am using the VPN provider Private Internet Access.
I am using the Raspberry Pi 4 with 4GB of RAM, performance on this upgraded board is great.
Anyways I am connecting to its service using systemd's openvpn-client @ US_New_York_City.service
I wonder if I can create a... (5 Replies)
Discussion started by: haloslayer255
5 Replies
LEARN ABOUT OSF1
mountdtab
mountdtab(4) Kernel Interfaces Manual mountdtab(4)
NAME
mountdtab - Table of local file systems mounted by remote NFS clients
SYNOPSIS
/etc/mountdtab
DESCRIPTION
The mountdtab file resides in the /etc directory and contains a list of all remote hosts that have mounted local file systems using the NFS
protocols. Whenever a client performs a remote mount, the server machine's mount daemon makes an entry in the server machine's mountdtab
file. The umount command instructs the server's mount daemon to remove the entry. The umount -b command broadcasts to all servers and
informs them that they should remove all entries from mountdtab created by the sender of the broadcast message. By placing an umount -b
command in a system startup file, mountdtab tables on NFS servers can be purged of entries made by a crashed client, who, upon rebooting,
did not remount the same file systems that it had before the system crashed. Tru64 UNIX systems automatically call umount -b at system
startup
The format for entries in the mountdtab file is as follows: hostname:directory Rather than rewrite the mountdtab file on each umount
request, the mount daemon comments out unmounted entries by placing a number sign (#) in the first character position of the appropriate
line. The mount daemon rewrites the entire file, without commented out entries, no more frequently than every 30 minutes. The frequency
depends on the occurrence of umount requests.
The mountdtab table is used only to preserve information between crashes and is read only by the mountd daemon when it starts up. The
mountd daemon keeps an in-core table, which it uses to handle requests from programs like showmount and shutdown.
RESTRICTIONS
Although the mountdtab table is close to the truth, it may contain erroneous information if NFS client machines fail to execute a umount -a
command when they reboot.
RELATED INFORMATION
mount(8), umount(8), mountd(8), showmount(8), shutdown(8) delim off
mountdtab(4)