Sponsored Content
Full Discussion: SCO 5.0 setup auto reboot
Operating Systems SCO SCO 5.0 setup auto reboot Post 302267623 by edfair on Friday 12th of December 2008 10:55:51 PM
Old 12-12-2008
Sometimes user applications leave stuff in that eventually causes the system to crash. If you had mentioned Syncronics/Realworld I would have known for certain and the weekly would have been just about right.

This is a 3 step process. First is a change in /usr/spool/cron/crontabs/root to add a line for the date and time plus the name of the file you wish to activate. I use reboot and put it in place of the standard one.
Then the reboot file itself with an init command to generate a reboot.
Then a modification to /etc/default/boot for the time delay and default level.

Mine go at 3:01 on Sunday morning to avoid the DST issue.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

SCO Unix printer waiting for auto-retry

Running SCO 5.0.5 with all the updates available on a Compaq 800 and just ran into this problem of the printer that is hooked up to /dev/lp0 &or /dev/lp. The printer has been working fine for 5 plus years and still works on another machine. I've uninstalled & re-installed the parallel port and... (0 Replies)
Discussion started by: cfaiman
0 Replies

2. SCO

Reboot the sco server

Dear sir, I am using sco open server 5.06.How we can reboot the system without using root password? Whar are the permision need to change to do this. Thanks, Mostafizur Rahman (3 Replies)
Discussion started by: rahmanm
3 Replies

3. Solaris

SB150 auto reboot

My SB150 machine rebooted itself this week several times, anyone have idea what the problem is, a blaster? :) kidding (2 Replies)
Discussion started by: howhowzz
2 Replies

4. Shell Programming and Scripting

Include xhost + at auto reboot script

Below is the startup/stop script for vncservers by end-user. How can xhost + command include in this script? Please help. Thank you. #!/bin/sh # # Startup/Stop script for vncservers for some users. # case "$1" in 'start') /bin/rm /tmp/.X11-unix/X0 /bin/su - applprod -c... (0 Replies)
Discussion started by: KhawHL
0 Replies

5. Solaris

IPMP setup removed, comes back with reboot

Hi all, I have 3 Sun v490's running Solaris 10. Each one has 2 zones on it. I changed the IP address and configuration on them this weekend, where ce0 was once the primary IP nic, now ce2 is. Previously, ce0 and ce4 were set up with IP multipathing, but I tried to remove that by changing the... (2 Replies)
Discussion started by: jackiea
2 Replies

6. SCO

SCO Reboot Issue

Hi, We are using SCO UNIX 7.1.3 and the server recently started rebooting by itself. Do anyone know how can i create a dump or crash dump while the server rebooots? Your quick help on this is really appreciated. Regards, Ravikumar R (1 Reply)
Discussion started by: rrb2009
1 Replies

7. SCO

SCO console login auto fills *

OS: SCO Openr Server 6.0 MP4 HW: Dell R710 Server When I try to login to the console, the login prompt keeps filling with * even when I presss enter after the password prompt the login starts filling automatically with the multiple asterisks. This is happening on the console only and if I... (0 Replies)
Discussion started by: atish0
0 Replies

8. Shell Programming and Scripting

Auto Remote SSH key setup

Hi Guys!! I am trying to get around the complex situation, i have a task to complete, Like to setup the remote SSH key automatically by providing the root login details, ip and ssh port once to the script input and once its tested and accepted the next ssh should be password less, script... (0 Replies)
Discussion started by: SilvesterJ
0 Replies

9. Red Hat

Disable xen machine to auto start on reboot

Hello Guys - I need to disable xen server not to start when the server is rebooted. 1) What is the parameter to be used to do this..below is the entry in my config file... on_reboot = "restart" 2) What is the default behaviors of the xen on reboot ? in case we comment this line from config... (0 Replies)
Discussion started by: saurabh84g
0 Replies

10. Solaris

Sysconfig setup window keeps showing after reboot

so here's teh deal: Solaris 11.3 zone created from a template created by configuring a zone, running sysconfig unconfigure on it and then saved by a zfs send and receive. create the new zoneconfig, import the template FS using zfs recieve. Now everytime we reboot the new zone it makes us do... (0 Replies)
Discussion started by: os2mac
0 Replies
reboot(1M)																reboot(1M)

NAME
reboot - restart the operating system SYNOPSIS
/usr/sbin/reboot [-dlnq] [boot_arguments] The reboot utility restarts the kernel. The kernel is loaded into memory by the PROM monitor, which transfers control to the loaded kernel. Although reboot can be run by the super-user at any time, shutdown(1M) is normally used first to warn all users logged in of the impending loss of service. See shutdown(1M) for details. The reboot utility performs a sync(1M) operation on the disks, and then a multi-user reboot is initiated. See init(1M) for details. On systems, reboot may also update the boot archive as needed to ensure a successful reboot. The reboot utility normally logs the reboot to the system log daemon, syslogd(1M), and places a shutdown record in the login accounting file /var/adm/wtmpx. These actions are inhibited if the -n or -q options are present. Normally, the system reboots itself at power-up or after crashes. The following options are supported: -d Force a system crash dump before rebooting. See dumpadm(1M) for information on configuring system crash dumps. -l Suppress sending a message to the system log daemon, syslogd(1M) about who executed reboot. -n Avoid calling sync(2) and do not log the reboot to syslogd(1M) or to /var/adm/wtmpx. The kernel still attempts to sync filesystems prior to reboot, except if the -d option is also present. If -d is used with -n, the kernel does not attempt to sync filesystems. -q Quick. Reboot quickly and ungracefully, without shutting down running processes first. The following operands are supported: boot_arguments An optional boot_arguments specifies arguments to the uadmin(2) function that are passed to the boot program and kernel upon restart. The form and list of arguments is described in the boot(1M) and kernel(1M) man pages.. If the arguments are specified, whitespace between them is replaced by single spaces unless the whitespace is quoted for the shell. If the boot_arguments begin with a hyphen, they must be preceded by the -- delimiter (two hyphens) to denote the end of the reboot argument list. Example 1: Passing the -r and -v Arguments to boot In the following example, the delimiter -- (two hyphens) must be used to separate the options of reboot from the arguments of boot(1M). example# reboot -dl -- -rv Example 2: Rebooting Using a Specific Disk and Kernel The following example reboots using a specific disk and kernel. example# reboot disk1 kernel.test/unix /var/adm/wtmpx login accounting file See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ mdb(1), boot(1M), dumpadm(1M), fsck(1M), halt(1M), init(1M), kernel(1M), shutdown(1M), sync(1M), syslogd(1M), sync(2), uadmin(2), reboot(3C), attributes(5) The reboot utility does not execute the scripts in /etc/rcnum.d or execute shutdown actions in inittab(4). To ensure a complete shutdown of system services, use shutdown(1M) or init(1M) to reboot a Solaris system. 11 Apr 2005 reboot(1M)
All times are GMT -4. The time now is 04:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy