03-29-2008
crontab -l <user_name>
I think root only that can reboot server, it may be some thing panic.
you should try investigate log in /var/adm/messages.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have compiled binary file using "cc" on SunOS 5.8 and the same binary file i have copied to SunOS 5.9 and it is giving me core dump error.I want to know whether migration of compiled code from lower version to higer version created this problem. how can i solve this problem.I am pasting the core... (1 Reply)
Discussion started by: Arvind Maurya
1 Replies
2. UNIX for Advanced & Expert Users
Good Morning.
The problem started after tha migration to a newer version of oracle - migration to oracle 9i. Before the migration jobs that were scheduled in crontabs were running ok. but after the migration they are not running.
I understand that is not easy to find out what the problem is.... (4 Replies)
Discussion started by: alexcol
4 Replies
3. Shell Programming and Scripting
Question for anyone that might be able to help:
My objective is to eheck if a file (a source file) exists in a directory. If it does then, I'd like to call an application (Informatica ETL file...not necessary to know) to run a program which extracts data and loads it into multiple targets.
... (6 Replies)
Discussion started by: jnanasakti
6 Replies
4. Red Hat
How to find out jobs scheduled by "at" command? (1 Reply)
Discussion started by: johnveslin
1 Replies
5. Shell Programming and Scripting
I had a cron file named mycron.cron and this file has cron jobs runs through out 365 days (jobs in the file mycron.cron run hourly, daily, weekly, monthly, quarterly and yearly). Is there an easy way to find what are the jobs scheduled today and what time they are scheduled to run?
Thanks in... (1 Reply)
Discussion started by: sureng
1 Replies
6. Shell Programming and Scripting
Hello All,
I'm new in shell scripting and would like to write an automated script that will check few jobs for the completion, and restart the process based on the jobs status. I am not quite sure how do I check the job status... Can someone please help? Any help will be appreciated. Thanks in... (1 Reply)
Discussion started by: mohullah
1 Replies
7. Red Hat
I've scheduled few jobs using cron. But they are not running .....
What might be the possible reasons ?? Also tell me how to troubleshoot.............
Please help me .......
Thanks in Advance. (2 Replies)
Discussion started by: vamshigvk475
2 Replies
8. Fedora
Hello, I have several cron jobs scheduled but looking at the results of running I see in some cases it takes more than 2 seconds, is there any way to adjust the accuracy of execution of cron?
Is there any other tool or way to fix the problem? (10 Replies)
Discussion started by: faka
10 Replies
9. Shell Programming and Scripting
Hi,
Is there any specific command to use to check only say Running jobs via autorep or similar command for Autosys? (0 Replies)
Discussion started by: sidnow
0 Replies
10. Shell Programming and Scripting
Hi Folks,
Please help me ,I need a unix shell script to check for multiple jobs running. if there are multiple backup Jobs running then it should be trigger an email .
Thanks,
Anand T (1 Reply)
Discussion started by: nandu67
1 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)