Sponsored Content
Top Forums Shell Programming and Scripting Avoiding rc.local file during reboot Post 302194827 by Smiling Dragon on Tuesday 13th of May 2008 07:28:32 PM
Old 05-13-2008
It sounds like you'll be ok doing a single user mode boot (init 1 or init s).
If all else fails, reboot from a cdrom or network and mount your root device onto /a.
 

9 More Discussions You Might Find Interesting

1. Solaris

different between soft reboot and hard reboot

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. Ubuntu

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... (1 Reply)
Discussion started by: eamani_sun
1 Replies

3. UNIX for Dummies Questions & Answers

Avoiding "file collision"

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

After reboot the .rhosts file in nobody nobody

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

Binary file for showing last reboot

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

Avoiding 'sh -c' when running ps from CRON

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

Avoiding the history

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

Avoiding file overwrite during file transfer using scp

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

Help with awk for selecting lines in a file avoiding repetition

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(2)						      BSD System Calls Manual							 REBOOT(2)

NAME
reboot -- reboot system or halt processor LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#include <unistd.h> #include <sys/reboot.h> int reboot(int howto); DESCRIPTION
The reboot() system call reboots the system. Only the super-user may reboot a machine on demand. However, a reboot is invoked automatically in the event of unrecoverable system failures. The howto argument is a mask of options; the system call interface allows the following options, defined in the include file <sys/reboot.h>, to be passed to the new kernel or the new bootstrap and init programs. RB_AUTOBOOT The default, causing the system to reboot in its usual fashion. RB_ASKNAME Interpreted by the bootstrap program itself, causing it to prompt on the console as to what file should be booted. Normally, the system is booted from the file ``xx(0,0)kernel'', where xx is the default disk name, without prompting for the file name. RB_DFLTROOT Use the compiled in root device. Normally, the system uses the device from which it was booted as the root device if possible. (The default behavior is dependent on the ability of the bootstrap program to determine the drive from which it was loaded, which is not possible on all systems.) RB_DUMP Dump kernel memory before rebooting; see savecore(8) for more information. RB_HALT the processor is simply halted; no reboot takes place. This option should be used with caution. RB_POWEROFF After halting, the shutdown code will do what it can to turn off the power. This requires hardware support. RB_INITNAME An option allowing the specification of an init program (see init(8)) other than /sbin/init to be run when the system reboots. This switch is not currently available. RB_KDB Load the symbol table and enable a built-in debugger in the system. This option will have no useful function if the kernel is not configured for debugging. Several other options have different meaning if combined with this option, although their use may not be possible via the reboot() system call. See ddb(4) for more information. RB_NOSYNC Normally, the disks are sync'd (see sync(8)) before the processor is halted or rebooted. This option may be useful if file system changes have been made manually or if the processor is on fire. RB_RDONLY Initially mount the root file system read-only. This is currently the default, and this option has been deprecated. RB_SINGLE Normally, the reboot procedure involves an automatic disk consistency check and then multi-user operations. RB_SINGLE prevents this, booting the system with a single-user shell on the console. RB_SINGLE is actually interpreted by the init(8) program in the newly booted system. When no options are given (i.e., RB_AUTOBOOT is used), the system is rebooted from file ``kernel'' in the root file system of unit 0 of a disk chosen in a processor specific way. An automatic consistency check of the disks is normally performed (see fsck(8)). RETURN VALUES
If successful, this call never returns. Otherwise, a -1 is returned and an error is returned in the global variable errno. ERRORS
[EPERM] The caller is not the super-user. SEE ALSO
crash(8), halt(8), init(8), reboot(8), savecore(8) HISTORY
The reboot() system call appeared in 4.0BSD. BUGS
The HP300 implementation supports neither RB_DFLTROOT nor RB_KDB. BSD
June 4, 1993 BSD
All times are GMT -4. The time now is 02:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy