07-31-2007
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
There is a posting similar to this but it does not list what resolved the issue.
When I log into the server, it shows the correct timezone (edt) but when jobs run from cron, it shows GMT.
Unix admin is looking for a solution.
I am looking for a short term workaround to get the jobs... (2 Replies)
Discussion started by: MizzGail
2 Replies
2. Shell Programming and Scripting
Hi,
i would like to ask if this cron is valid.
40 3-6,8-23 * * * /my command i want my job to run every hour on the 40th minute except 740am. Is this correct? (1 Reply)
Discussion started by: new2ss
1 Replies
3. UNIX for Dummies Questions & Answers
Hi Guys,
can someone help me how to setup a job in cron that runs each morning from 8-10 a.m. for every half an hour but starting from 8:50 a.m.?
so far i have this:
00,30 8-10 * * *
but the problem is that it starts at 8:30 instead of 8:50
Anyone?
Thanks! (1 Reply)
Discussion started by: netrom
1 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I have been searching for older posts and I've found many entries with identical problems, but I was not able to find the solution (or when I thought I found it, my trial didn't worked :(). Anyway, here is my question.
I wrote a sftp.sh file that runs perfect from command line. It uses scp... (6 Replies)
Discussion started by: Kronos
6 Replies
5. UNIX for Advanced & Expert Users
how can we identify the task completion time which was initiated by CRON.
we have 1000 of jobs whihc are runing from cron so it is not feasable to edit every cron entry or every script to add the respective code to find teh completion time.
Can some one please provide a inut to find the task... (3 Replies)
Discussion started by: NIMISH AGARWAL
3 Replies
6. Shell Programming and Scripting
currently i have this cron on my informix db
00 00,01,03,06,08,09,10,11,12,13,14,16,18,19,20,21,22,23 * * * . /informix/script.sh
it was working until last february22, the last run was 1:00AM. It was suppose to run 3:00, 6:00, so on..
last night we restarted it and for some reason the cron... (2 Replies)
Discussion started by: lhareigh890
2 Replies
7. Shell Programming and Scripting
Hi
Is it possible to run different cron jobs at the same time? It appears that when I run ones at 15 min granularity that they may prevent ones running later in the day.
Should crons run at same time have impact on one another? (4 Replies)
Discussion started by: rob171171
4 Replies
8. Solaris
On Solaris 10 server the system date won't match with the timestamp on files created by a cron jobs, Please help
here is what i get when i check for system date
infodba-ie10ux014:/tcpdv1_ie10/tcadmin/bin\n\r-> date
Tue Apr 24 15:27:43 GMT 2012at same time i executed a cron job, and checked... (4 Replies)
Discussion started by: karghum
4 Replies
9. Shell Programming and Scripting
Hi,
1)
If some job supposed to run on 1st of every month at 7 AM
In cron job when we have a blackout on the 1st ( i.e when 1st falls on a sunday ) how can we make the job run the next business day?
2) How can we run a job on 25th of every quarter 7 AM(jan,apr,jul,oct)
And if 25th... (5 Replies)
Discussion started by: System Admin 77
5 Replies
10. UNIX for Dummies Questions & Answers
Hello gurus,
I am making what I think is a simple db2 call from within a shell script but I am having difficulty producing the desired
report when I run the script shown below from a shell script in cron. For example, my script and the crontab file setup
is shown below:
#!/bin/ksh
db2... (3 Replies)
Discussion started by: okonita
3 Replies
LEARN ABOUT HPUX
show_server
show server(1m) show server(1m)
NAME
show server - Displays attribute information about the server running on the local system
SYNOPSIS
cdscp show server
DESCRIPTION
The show server command displays all the names and values from the attributes named in this entity. The server must be enabled when you use
this command. The following are valid attribute names: Specifies the number of times the server was unable to contact all the clearing-
houses that store a replica of a particular child directory's parent directory and apply the child updates that have occurred since the
last skulk. This counter is incremented by the Cannot Update Child Pointer event. Specifies the time when the CDS control program process
was started. Specifies the number of times a user attempted (from this server) to remove a replica that is crucial to the connectivity of
a directory hierarchy. The server background process prevents users from accidentally disconnecting lower-level directories from higher-
level directories. When it detects an attempt to remove a crucial replica, it does not execute the command to do so. This counter is incre-
mented by the Crucial Replica event. Specifies the maximum amount of time that a timestamp on a new or modified entry can vary from local
system time at the server system. Specifies the clearinghouse or clearinghouses known to the server. Specifies the number of read opera-
tions directed to this CDS server. Specifies the number of times a server principal for this server was found to have inadequate permis-
sions to perform a requested operation. Specifies the number of skulks successfully completed by this CDS server. Specifies the number of
skulks initiated by this CDS server. Specifies the number of broken connections between clearinghouses on this server and clearinghouses
closer to the root. Incoming requests to this server that require a downward lookup in the directory hierarchy still succeed, but requests
that require a lookup in directories closer to the root will fail. This counter is incremented by the Broken Lookup Paths event. Specifies
the number of write operations to this CDS server.
Privilege Required
You must have read permission to the server.
NOTE
This command may be replaced in future releases by the dcecp command, and may no longer be supported at that time.
EXAMPLE
The following command displays the current values of all the attributes associated with the server running on the local system: cdscp> show
server
SHOW
SERVER
AT 1991-10-15-15:56:47
Creation Time = 1991-10-15-15:39:35.35
Future Skew Time = 300
Read Operations = 757
Write Operations = 542
Skulks Initiated = 219
Skulks Completed = 219
Times Lookup Paths Broken = 1
Crucial Replicas = 0
Child Update Failures = 1
Security Failures = 0
Known Clearinghouses = /.../abc.com/Boston_CH
= /.../abc.com/NY_CH
RELATED INFORMATION
Command: disable server(1m)
show server(1m)