05-13-2008
Avoiding rc.local file during reboot
Hi,
I am tryin to install custom software during the linux reboot.
So,I have changed rc.local file, but unfortunately I have added a code that
is going on a infinite loop. And now I am in a pick.
Is there anyway that I can avoid rc.local file while reboot.
Can anyone help me with this?
Thanks,
Sunny
9 More Discussions You Might Find Interesting
1. Solaris
Hi Guru's
Can any want here could explain to me the different between soft reboot and hard reboot .
Best Regards
Seelan (3 Replies)
Discussion started by: seelan3
3 Replies
2. Shell Programming and Scripting
Hi,
I am tryin to install custom software during the linux reboot.
So,I have changed rc.local file, but unfortunately I have added a code that
is going on a infinite loop. And now I am in a pick.
Is there anyway that I can avoid rc.local file while reboot.
Can anyone help me... (2 Replies)
Discussion started by: eamani_sun
2 Replies
3. UNIX for Dummies Questions & Answers
I don't know if there's a better name for what I call "file collision"... Basically, I have a script that I'm using for quick and dirty MySQL testing. Here's the idea...
#!/usr/local/bin/bash
for num in `jot $1` ## Yep, jot... this is FreeBSD
do
/usr/bin/time mysql --user=root... (2 Replies)
Discussion started by: treesloth
2 Replies
4. Solaris
Hi All,
I have a station in solaris 10 in a environnemet NIS. after reboot of the station the file ". rhosts" has the UID / GID nobody.
Could you please help me to find the solution?
Thx.
Vince (0 Replies)
Discussion started by: Vince78
0 Replies
5. Solaris
Does anyone know what is the binary file for seeing the last reboot since my wtmpx file has been dumped as of now and i am not able to see the last reboot with the command "last reboot".
Please don't say uptime, since i want to see the last 4-5 reboots for this server.
Thanks in advance (4 Replies)
Discussion started by: aksijain
4 Replies
6. Shell Programming and Scripting
Hi,
I have a script which has the below line:
ps -ef | grep ${SCRIPT_NAME} | grep ksh | grep -v grep >> /tmp/instance.tmp
When the script is invoked through CRON, I get 2 lines in instance.tmp when actually only one instance is running:
cdrd 17790 17789 0 15:14:01 ? 0:00 /bin/ksh... (8 Replies)
Discussion started by: cavallino4u
8 Replies
7. UNIX for Dummies Questions & Answers
In bash shell, how we can avoid the commands getting recorded in history file.
One way i can think of is :
export HISTSIZE=0
Is there any other way to achieve this?
Thanks (1 Reply)
Discussion started by: pandeesh
1 Replies
8. Shell Programming and Scripting
Hi,
I have written a small script to transfer a file from one unix server to other using scp command which is working fine. As I know with scp, if any file with the same name is already present on destination server, it would get overwritten without any notification to user. Could anyone help me... (14 Replies)
Discussion started by: dsa
14 Replies
9. Shell Programming and Scripting
Hello,
I am using Awk in UBUNTU 12.04.
I have a file as following with 48,432,354 lines and 4 fields.
The file has this structure (There are repetitions of the first column in several lines)
AB_14 S54 A G
AB_14 S55 A A
AB_14 S56 G G
GO_15 S45 T A
GO_15 S46 A A
PT_16 S33 C C
PT_16 ... (4 Replies)
Discussion started by: Homa
4 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)