09-01-2018
Hi,
I'm not entirely clear on what could have caused a reboot here - from the output you've provided it seems that after five seconds the script proceeded to kill the previously-backgrounded command. If you can give us a bit more info on what went wrong, what necessitated a reboot, and how this came about then I'd be happy to offer further suggestions as to how to proceed.
5 More Discussions You Might Find Interesting
1. Linux
I have a PC that was built in Europe pre-installed with Windows 2000.
The HDD is 40GB, but, its split up as two 20GB (Taken up by Windows). I want to take over my Mandrake 9.1 CDs and install Linux on that machine.
My question is, how would I proceed to install Linux this way???
Now, If... (1 Reply)
Discussion started by: wardialer
1 Replies
2. Shell Programming and Scripting
help
I am having text file like this...
------------------------END OF UPDATION ------------------
xxxxxxxxxxxxxxxxxxxxxxxxx
yyyyyyyyyyyyyyyyyyyyy
yyyyyyyyyyyyyyyyyyyyy
1 row updated
------------------------END OF UPDATION ------------------
TTTTTTTTTTTTTTTT
FFFFFFFFFFFFFFFFF
... (3 Replies)
Discussion started by: suryanarayana
3 Replies
3. Shell Programming and Scripting
Is there a way to bring the terminal script to the front? I am running this script through OMCEdit which is then running it through Terminal. I have some dialog boxes (using osascript) and the dialog boxes are not coming to the front...Terminal bounces and I have to click on Terminal to see the... (1 Reply)
Discussion started by: mainegate
1 Replies
4. Shell Programming and Scripting
#include<header.h>
void classname :: pvvd_init
( abcd
,efgh
,ijkl
,mnop )
{
rvcl_tabl_name_tabl.pvvd_init
( xxxx
,"tabl_mame" ) ;
... (2 Replies)
Discussion started by: ultimatix
2 Replies
5. UNIX for Dummies Questions & Answers
When I choose to encrypt my drive during a Linux install, it encryps it, but I receive errors in dmesg and in ~/.xsessions-errors during use. The first error is in dmesg where it sometimes shows errors writing to the encypted device. The second error is in ~/.xsessions-errors with an error about... (0 Replies)
Discussion started by: justgoogleit
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)