12-14-2011
We don't know your system, or what version of Solaris you have, or what Shell you (or your cron) uses.
Please post what you normally type when you shut your system down.
5 More Discussions You Might Find Interesting
1. Solaris
I have compiled my application on Solaris 10 with following description
SunOS ldg1 5.10 Generic_138888-03 sun4v sparc SUNW,Sun-Blade-T6320
The compiler is Sun C++ 5.9 SunOS_sparc Patch 124863-01 2007/07/25
But when installing the application on Solaris 9
SunOS odcarch02 5.9... (2 Replies)
Discussion started by: ash_bit2k2
2 Replies
2. Solaris
Hi,
I am unable to login into my terminal hosting Solaris 10 and get the below error message
"Server refused to allocate pty
ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory "
Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies
3. Solaris
Hi,
I am running into a some problems creating a dual boot system of 2 solaris instances using ZFS file system and I was wondering if someone can help me out.
First some back ground. I have been asked to change the file system of our server from UFS to ZFS. Currently we are using Solaris... (3 Replies)
Discussion started by: estammis
3 Replies
4. Solaris
Got a strange problem.
I have 4 Solaris servers all configured the same, Solaris 10 x86 update 10.
When I try to ssh from one Solaris 10 server to another server ssh hangs.
I have an identical server and when I try this everything works fine.
The weird thing is if I am root on the server... (1 Reply)
Discussion started by: ccj4467
1 Replies
5. Solaris
Hi Gurus
I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow.
Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently... (1 Reply)
Discussion started by: nick101
1 Replies
CRON(8) System Manager's Manual CRON(8)
NAME
cron - clock daemon
SYNOPSIS
/usr/sbin/cron
DESCRIPTION
Cron executes commands at specified dates and times according to the instructions in the files /etc/crontab and /etc/crontab.local. None,
either one, or both of these files may be present. Since cron never exits, it should only be executed once. This is best done by running
cron from the initialization process through the file /etc/rc; see init(8).
The crontab files consist of lines of seven fields each. The fields are separated by spaces or tabs. The first five are integer patterns
to specify:
o minute (0-59)
o hour (0-23)
o day of the month (1-31)
o month of the year (1-12)
o day of the week (1-7 with 1 = Monday)
Each of these patterns may contain:
o a number in the range above
o two numbers separated by a minus meaning a range inclusive
o a list of numbers separated by commas meaning any of the numbers
o an asterisk meaning all legal values
The sixth field is a user name: the command will be run with that user's uid and permissions. The seventh field consists of all the text
on a line following the sixth field, including spaces and tabs; this text is treated as a command which is executed by the Shell at the
specified times. A percent character (``%'') in this field is translated to a new-line character.
Both crontab files are checked by cron every minute, on the minute.
FILES
/etc/crontab
/etc/crontab.local
7th Edition October 23, 1996 CRON(8)