You will need to change the timezone on a job-by-job basis.
The TZ line should not be a line on its own in crontab, but it can be part of a normal line in crontab or be inside a script.
Quote:
Set TZ=Asia/Calcutta
The syntax you show for TZ is incorrect.
What do you get in a normal interactive session for:
What Operating System and version are you running?
What Shell are you running?
Is your server clock set in UTC with default timezone in /etc/TIMEZONE ?
It is often easier to use the cron on a server which runs in the target timezone to trigger jobs on the server which is in a different timezone.
Hi,
I'm new to shell script programming, I only have Java programming background.
I'm writing a shell script to do file synchronization between 2 machines that located at different time zone area. Both machine were set its time zone according to its geographical location (Eg: server is at... (1 Reply)
I have a cluster of two Solaris server (veritas cluster). one working and the other is standby
I am going to change the date on them , and am looking for a secure solution as it is giving an important service.
my opinion is that the active one doesn't need to be restarted (if I don't change the... (1 Reply)
can some one help me out as it is showing 2 different time zones in global zone and nonglobal zone .In global zone it is showing in GMT while in nonglobal zone i it showing as PDT.
System in running with solaris 10 (3 Replies)
Hello,
On our Solaris 10 servers we have shared NIC interfaces. We have a program that is having issues talking to the all zones because they have the same MAC address.
Is there a way with zonecfg or ifconfig to change the MAC on the zones?
Other wise we need to rewire the servers and I don't... (4 Replies)
Hi guys thanks for the help for my previous posts.Now i have a requirement that i download a XMl file which has UTC time stamp.I need to convert UTC time into Unix server timezone.
For ex if the time zone of unix server is CDT then i need to convert into CDT.whatever may be the system time... (5 Replies)
Hi,
I created some cron entries in one of the 4 zones in Solaris 10. Now I want to edit it and unable to find the crontab file
crontab -l gives : unable to open crontab file
/usr/spool/cron/crontabs doesn't have the crontab file
Hence, I did ifconfig -a and tried to login with the 3... (2 Replies)
Hi,
First post.
I have a script that I am having a little trouble with and I hope someone can help.
I will post the code for your input, but I want to read the lines of a file and use this as input to a command in a while loop...
#!/bin/sh
#
#
### Variables
MSG=/tmp/tmptest.txt... (7 Replies)
Discussion started by: dakelly
7 Replies
LEARN ABOUT OPENDARWIN
queuedefs
queuedefs(4) File Formats queuedefs(4)NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1: A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can
have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO at(1), crontab(1), nice(1), cron(1M)SunOS 5.10 1 Mar 1994 queuedefs(4)