autoboot system problem Post: 302722143

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Ping problem. system down!!

I wrote a script to test many systems to see if they are up or not. if a system is down, i am notified by email now, most of the time,when systems are down in my enviroment, it is because the user accidentally or purposely (not knowing the consequences) hit the power button. so these problems...

2. AIX

Problem cloning system

Hi everyone, I want to clone a AIX 5.2 system from a machine to another one. So i modified bosinst.data and image.data files (according to future platform) before making mksysb on old platform. After booting on CD and restoring system using mksysb tape, the installation is launched but ever...

3. Programming

Problem in system call

Dear Friends, I write a c program to list the directories recursively. For this I write a function called my_readdir to read the content of directory. For this I use read system call it returns -1, then I use readdir system call it gives comment terminated error or segmentation...

4. Solaris

Secure FTP Problem using Sun SSH on Client system F-Secure on Server system

I am using shell script to do secure ftp. I have done key file setup to do password less authentication. Following are the FTP Details: FTP Client has Sun SSH. FTP Server has F-Secure. I am using SCP Command to do secure copy files. When I am doing this, I am getting the foll error scp:...

5. Linux

system call problem

hi, where can I find the detail information about the syscall in binary instructions of linux/mips. for example, in linux/mips: li v0, 4140 syscall it's a syacall of "lseek" , but how can I find that which registers will be used in this syscall , and the meaning of the arguments in the...

6. Linux

file system access problem

I have 3 windows partitions (c,d,e) all of NTFS file system i mounted them while installing open suse in /win/c,/win/d,/win/e created a user other than "root" eg: "us1" problem 1: by loggimg into linux by user "us1" iam unable to see files in mounted...

7. UNIX for Advanced & Expert Users

problem with restarted I/O system calls

Greetings. Suppose I have a UNIX OS with automatic-restart (by default) of interrupted system calls, or I use sigaction() with SA_RESTART flag. If I am in the middle of a read(fd1, buf1, MAXSIZE) or a write(fd2, buf2, MAXSIZE), and I am interrupted by a signal, then the system will...

8. Programming

Problem on capturing system Shutdown

I am having exactly the same problem with https://www.unix.com/programming/129264-application-cleanup-during-linux-shutdown.html but the thread is old and closed. The only difference is that I use sigaction() instead of signal(), which is recommended, as far as I know. This is my code: ...

9. Red Hat

Problem registering a new system

Hi, A registered a new system the other day using the subscription-manager (RedHat ES6, Academic edition) but it's not showing up on the web site so that I can entitle it and get updates, etc. Any ideas? ~ Rob

LEARN ABOUT OSX

halt

REBOOT(8)						    BSD System Manager's Manual 						 REBOOT(8)

NAME

     halt, reboot -- stopping and restarting the system

SYNOPSIS

     halt [-lnqu]
     reboot [-lnq]

DESCRIPTION

     The halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM (and subsequently a SIGKILL) and,
     respectively, halt or restart the system.	The action is logged, including entering a shutdown record into the wtmp(5) file.

     When the system is halted with the halt command, the system is powered off.

     The options are as follows:

     -l      The halt or reboot is not recorded in the system log.  This option is intended for applications such as shutdown(8), that call reboot
	     or halt and log this themselves.

     -n      The file system cache is not flushed.  This option should probably not be used.

     -q      The system is halted or restarted quickly and ungracefully, and only the flushing of the file system cache is performed (if the -n
	     option is not specified).	This option should probably not be used.

     -u      The system is halted up until the point of removing system power, but waits before removing power for 5 minutes so that an external
	     UPS (uninterruptible power supply) can forcibly remove power.  This simulates a dirty shutdown to permit a later automatic power on.
	     OS X uses this mode automatically with supported UPSs in emergency shutdowns.

     Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending
     doom and cleanly terminating specific programs.

SIGTERM TO SIGKILL INTERVAL

     The SIGKILL will follow the SIGTERM by an intentionally indeterminate period of time.  Programs are expected to take only enough time to
     flush all dirty data and exit.  Developers are encouraged to file a bug with the OS vendor, should they encounter an issue with this func-
     tionality.

SEE ALSO

     wtmp(5), shutdown(8), sync(8)

HISTORY

     A reboot utility appeared in Version 6 AT&T UNIX.

BSD
								   June 9, 1993 							       BSD