11-29-2006
Your shot in the dark was not far off. Turns out there is a Linux server that it's mounted to, or somehow connected to for backup of data. That machine was down suffering from a bad power cord, making it unreachable.
Thanks for your reply.
9 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Hi all,
Just started holidays (ya!) and Murphy's Law has kicked in already (doh!).
I'm looking after (when at work) two SCO 5.0.5 Systems running on Netfinity 5500 Servers (Model # 8662-3RY). Every once and a while the production server just reboot's itself. There is no mention of a cause... (8 Replies)
Discussion started by: Cameron
8 Replies
2. Programming
Hello all,
I have the following question:
if you join a multicast group (with setsockopt() and IP_ADD_MEMBERSHIP) and specify INADDR_ANY as network interface to join on, the kernel is supposed to choose which interface to use (if there are multiple network interfaces, of course).
Does... (2 Replies)
Discussion started by: AlexI
2 Replies
3. UNIX for Dummies Questions & Answers
Hi,
Can someone advise me how to find the last system rebooted date(s)? Thanx N Regards,
Hush (2 Replies)
Discussion started by: hush
2 Replies
4. AIX
I've recently changed my gateway setting using SMIT. Everything went fine except that the gateway setting kept reverting back to the old one everytime I reboot the server.
I'm on AIX 5.2 running p-Series. Thanks for any info. (3 Replies)
Discussion started by: dereklow
3 Replies
5. Solaris
dear all,
I have 2 T2000 with solaris 10 and oracle 10g installed on it. these two servers are rebooted by itself.
could anyone help me investigate the cause.
the message log is attached
thanx, (3 Replies)
Discussion started by: fsmadi
3 Replies
6. Solaris
Hello Everyone ,
I am a new member to this forum and came to know about this from so many of my friends . I face one issue last day when suddenly the system got rebooted ( But don,t know why ) . Can someone please help me in investigating this issue as to why the system got rebooted and who... (4 Replies)
Discussion started by: gera_sachin125
4 Replies
7. Linux
Hi,
Once again I came to get rescued in a situation where one of my workstations has this ierd thing that "xinetd" won't start at reboot or shutdown. I have done the follwoing but no change in results.
chkconfig --list xinetd
xinetd 0:off 1:off 2:on 3:on 4:on 5:on ... (2 Replies)
Discussion started by: harjitsingh
2 Replies
8. Solaris
Hi all,
i want to know the procedure reboot the server through console if the system is completely down.Please help me if anybody knows this. I would really thanfull to all.
regards
Krishna Murthy (1 Reply)
Discussion started by: murthy76
1 Replies
9. UNIX for Dummies Questions & Answers
hi there. new problem for me!!! i have been using a Sabayon Linux 3.5 distribution and yesterday when i turned the system on it stopped responding, i mean it freeazed. i was listening to music on Audacious and suddenly the system is ice cold...baby. what to do. Since i've tried 'reiserfsck' the... (0 Replies)
Discussion started by: dvas83
0 Replies
REBOOT(8) System Manager's Manual REBOOT(8)
NAME
reboot - reboot the system immediately
SYNOPSIS
reboot [-f]
DESCRIPTION
Reboot can be used to reboot the system after installing a new kernel. It does not inform the users, but does log it's actions in
/usr/adm/wtmp and /usr/adm/authlog. The system is then rebooted with the reboot(2) systemcall.
If the -f flag is not given then all processes are sent terminate signals to give them a chance to die peacefully before the reboot() call.
If the wtmp file exists, reboot logs itself as if it were a shutdown. This is done to prevent last(1) from talking about system-crashes.
Reboot is registered as is in the authlog file.
Reboot can only be executed by the super-user. Any other caller will be refused, either by reboot(8) or by reboot(2).
SEE ALSO
reboot(2), shutdown(8), halt(8), boot(8).
BUGS
The error message's given by reboot are not always useful. There are several routines that can fail, but which are not fatal for the pro-
gram.
AUTHOR
Edvard Tuinder (v892231@si.hhs.NL)
REBOOT(8)