Multple crons at boot

10 More Discussions You Might Find Interesting

1. Red Hat

Handling multple profiles with single user account

Team , I would like to handle multiple profiles(.profile/.kshrc, .profile1/.kshrc1..etc) with single user account as 'useradm' in same server. for example : firstly login into server with useradm account it has to load .profile/.kshrc or profile1/.kshrc1, set the environment...

2. UNIX for Dummies Questions & Answers

Execution Problems with Crons

Buddies, cron is not executing any monitoring scripts for 'Oracle' user in Red Hat Linux 5. Details about the cron job :- oracle@localhost ~]$ crontab -l 15 7 * * * /home/oracle/tab.sh The tab.sh script when firing manually is working fine. Any inputs/advice will be great for me.

3. Boot Loaders

Reboot and Select Proper Boot device or insert Boot media in select Boot device and press a key

Hello, I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error " reboot and select proper Boot device or insert Boot media in select Boot device and press a key " I have tried CD and...

4. Shell Programming and Scripting

Reading passwd and need to use it multple times when script asks

Hi Gurus, I have one requirment.. I have written a script and it asks a registry passwd while performing some clearcase command. Now we are giving it manually. It's for one time run. We want to perform this for multiple times on multiple files throguh for loop.. means we need to pass the same...

5. UNIX for Dummies Questions & Answers

Crons -Last run time and errorlog

Hi There are few crons running under my account. How to check the last run time of the Cron and if it has run successfully without any errors. Also if there are any errors while running, will the errors be stored some where? How to check the status of all the Crons? Thanks Ashok

6. Shell Programming and Scripting

Working With Crons

It said I had to approve them through here or something because they won't work and everyone on my site Is gettin pissed off. Please help

7. UNIX for Dummies Questions & Answers

Figuring out Crons

Hello, I've built a news site using SimplePie to pull in a set of feeds and display them on a page. The caching is working but the problem is that the first initial load is slow. After that, you can hit refresh and it loads very quickly. I'd like to eliminate that first slow load by creating a...

8. UNIX for Dummies Questions & Answers

Crons executed multiple times.

For some reason my crons are being executed twice. Any suggestion?? I'm currently on 5.8

9. Solaris

solaris boot problem boot error loading interpreter(misc/krtld)

When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error. cannot find mis/krtld boot error loading...

10. UNIX for Advanced & Expert Users

Cannot boot - Boot : Panic : File size out of range (EWS-UX/V unix)

Hey ! I am running EWS-UX/V (Rel 4.2) on NEC EWS/4800/330 station and I am having problems rebooting my station : I am getting the following message on display : BOOT : PANIC : File size out of range. According to user guide, this error is occuring when a file exceeding the limit and/or...

LEARN ABOUT BSD

fastboot

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

NAME

       reboot - stopping and restarting the system

SYNOPSIS

       /sbin/reboot [ -lqnhdarsfRD ]
       /sbin/halt [ -lqndars ]
       /sbin/fastboot [ -lqndarsRD ]

DESCRIPTION

       2.11BSD	is started by placing it in memory at location zero and transferring to its entry point.  Since the system is not reentrant, it is
       necessary to read it in from disk or tape each time it is to be boot strapped.

       Rebooting a running system: When the system is running and a reboot is desired, shutdown(8) is normally used to stop time sharing  and  put
       the system into single user mode.  If there are no users then /sbin/reboot can be used without shutting the system down first.

       Reboot  normally  causes the disks to be synced and allows the system to perform other shutdown activities such as resynchronizing hardware
       time-of-day clocks.  A multi-user reboot (as described below) is then initiated.  This causes a system to be booted and an  automatic  disk
       check to be performed.  If all this succeeds without incident, the system is then brought up for multi-user operation.

       Options to reboot are:

       -l     Don't try to tell syslogd(8) what's about to happen.

       -q     Reboot quickly and ungracefully, without shutting down running processes first.

       -n     Don't sync before rebooting.  This can be used if a disk or the processor is on fire.

       -h     Don't reboot, simply halt the processor.

       -d     Dump memory onto the dump device, usually part of swap, before rebooting.  The dump is done in the same way as after a panic.

       -a     Have the system booter ask for the name of the system to be booted, rather than immediately booting the default system (/unix).

       -r     Mount the root file system as read only when the system reboots.	This is not supported by the kernel in 2.11BSD.

       -s     Don't enter multi-user mode after system has rebooted - stay in single user mode.

       -f     Fast reboot.  Omit the automatic file system consistency check when the system reboots and goes multi-user.  This is accomplished by
	      passing a fast reboot flag on to the rebooting kernel.  This currently prevents the use of -f flag in conjunction with the -h (halt)
	      flag.

       -D     Set the autoconfig(8) debug flag.  This is normally not used unless one is debugging the autoconfig program.

       -R     Tells  the  kernel  to  use  the	compiled  in  root  device.   Normally	the system uses the device from which it was booted as the
	      root/swap/pipe/dump device.

       Reboot normally places a shutdown record in the login accounting file /usr/adm/wtmp.  This is  inhibited  if  the  -q  or  -n  options  are
       present.   Note	that  the -f (fast reboot) and -n (don't sync) options are contradictory; the request for a fast reboot is ignored in this
       case.

       Halt and fastboot are synonymous with ``reboot -h'' and ``reboot -f'', respectively.

       Power fail and crash recovery: Normally, the system will reboot itself at power-up or after crashes if  the  contents  of  low  memory  are
       intact.	 An  automatic	consistency  check of the file systems will be performed, and unless this fails, the system will resume multi-user
       operations.

SEE ALSO

       autoconfig(8), sync(2), utmp(8), shutdown(8), syslogd(8)

3rd Berkeley Distribution					   May 24, 1996 							 REBOOT(8)

SCO