Cron to run 3rd Tuesday of every odd months Post: 302914392

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

root cron was override w/ 3rd party software

Hi Guys, I'm new in Unix Environment. Any Unix Guru around...I need help. My question is, is it possible that the root cron could be override with 3rd party software?How can it happen. Another thing, how the cron job works?, I mean how the Unix process the cron job , I don't have an idea...

2. UNIX for Dummies Questions & Answers

Where does cron run from?

I have a script in the same directory as some files and directories im trying to tar up and I have it run in cron. Well it runs but says it can't find the directories, you need to be in the directory where the script is for it to work. Here is my cron and script its crappy but it does the trick =)....

3. Shell Programming and Scripting

Cron to run first day of month to calculate date 3 months ago

Hi, I would like to find out how can i calculate a date which is 3 months ago. I intend to run a cron job on the 1st of every month, and calculate the month 4 months earlier from the date. For example, if today's date is 1st May 2007, i would like to return 012007( January 2007). i can get...

4. UNIX for Dummies Questions & Answers

cron does not appear to run

Hi everyone, I am having a problem with a cron, I am using Solaris 10 and need to run a php file every 5 minutes. I can run the file from the test user, but the cron does not seem to run. I do not see anything about it in /var/cron/log but see crons for other users running. What should I look...

5. Shell Programming and Scripting

how to schedule the cron only if tuesday doesnot fall under 5 th and 25 th of jan

Hi I am new to unix. I have to set up a cron for the program , which should run every Monday at 3 a.m, however , if the date is between the 5 th and the 15th of January,APril or December, the program should not run I know i cant do this in cron , Help with writing the if contion is...

6. UNIX for Dummies Questions & Answers

[Solved] Cron - job to run every 3rd Friday of the month only

Hi Expert Please help me to set a cron job schedule, Ihave a job that run every 3rd Friday of the month at 1030am. I tried to set up like this, but the job still runs every friday at 1030am. I want the job to run every 3rd Friday of the month at 1030am only 30 10 15,16,17,18,19,20,21...

7. Shell Programming and Scripting

Who -u gives different output if run from cron than if run from terminal?

If I run 'who -u' interactively or from a script invoked through bash in a tty on my Ubuntu 12LTS box I get an output like this: testuser pts/0 Dec 9 02:32 . 2163 (host.xx.yy) running the same through cron I get: testuser pts/0 2012-12-09 02:32 00:05 2163...

8. Shell Programming and Scripting

Odd results when my script runs from cron..

Hi folks, So I wrote a script to run "top", "awk" out values fro the "top" and send the results to a data file. I then set it to run in cron every 15 minutes. Now I'm noticing that the script, and it's sub-commands are not always cleanly finishing and, in my investigations, I am also...

9. Shell Programming and Scripting

Cron job - Need to run Cron every quarter at particular time

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...

10. AIX

cron job on 3rd sunday of every month

Hi, Actually scheduled my test scripts on test severs as shown below. They are supposed to run on 3rd sunday of every month. Unfortunately it ran on 2nd sunday of the month (suspecting that it will run every sunday). I am sorry if I miss something. Could you please let me know if I did any...

LEARN ABOUT NETBSD

iptest

IPTEST(1)						      General Commands Manual							 IPTEST(1)

NAME

       iptest - automatically generate packets to test IP functionality

SYNOPSIS

       iptest [ -1234567 ] [ -d <device> ] [ -g <gateway> ] [ -m <MTU> ] [ -p <pointtest> ] [ -s <source> ] <destination>

DESCRIPTION

       iptest ...

OPTIONS

       -1     Run  IP  test  group  #1.   This group of tests generates packets with the IP header fields set to invalid values given other packet
	      characteristics.	The point tests are: 1 (ip_hl < ip_len), 2 (ip_hl > ip_len), 3 (ip_v < 4), 4 (ip_v > 4), 5 (ip_len  <  packetsize,
	      long  packets),  6 (ip_len > packet size, short packets), 7 (Zero length fragments), 8 (packet > 64k after reassembly), 9 (IP offset
	      with MSB set), 10 (ttl variations).

       -2     Run IP test group #2.  This group of tests generates packets with the IP options constructed with invalid values given other  packet
	      characteristics.	The point tests are: 1 (option length > packet length), 2 (option length = 0).

       -3     Run  IP  test  group  #3.   This group of tests generates packets with the ICMP header fields set to non-standard values.  The point
	      tests are: 1 (ICMP types 0-31 & 255), 2 (type 3 & code 0 - 31), 3 (type 4 & code 0, 127, 128, 255), 4 (type 5 & code  0,	127,  128,
	      255),  5	(types	8-10,13-18  with  codes 0, 127, 128 and 255), 6 (type 12 & code 0, 127, 128, 129, 255) and 7 (type 3 & codes 9-10,
	      13-14 and 17-18 - shortened packets).

       -4     Run IP test group #4.  This group of tests generates packets with the UDP header fields set to non-standard values.  The point tests
	      are:  1  (UDP  length  >	packet	size), 2 (UDP length < packetsize), 3 (sport = 0, 1, 32767, 32768, 65535), 4 (dport = 0, 1, 32767,
	      32768, 65535) and 5 (sizeof(struct ip) <= MTU <= sizeof(struct udphdr) + sizeof(struct ip)).

       -5     Run IP test group #5.  This group of tests generates packets with the TCP header fields set to non-standard values.  The point tests
	      are:  1  (TCP  flags  variations,  all  combinations),  2  (seq  =  0,  0x7fffffff, 0x8000000, 0xa0000000, 0xffffffff),  3 (ack = 0,
	      0x7fffffff, 0x8000000, 0xa0000000, 0xffffffff), 4 (SYN packet with window of 0, 32768, 65535), 5 (set urgent pointer to  1,  0x7fff,
	      0x8000, 0xffff), 6 (data offset), 7 (sport = 0, 1, 32767, 32768, 65535) and 8 (dport = 0, 1, 32767, 32768, 65535).

       -6     Run IP test group #6.  This test generates a large number of fragments in an attempt to exhaust the network buffers used for holding
	      packets for later reassembly.  WARNING: this may crash or cause serious performance degradation to the target host.

       -7     Run IP test group #7.  This test generates 1024 random IP packets with only the IP version, checksum, length  and  IP  offset  field
	      correct.

       -d <interface>
	      Set the interface name to be the name supplied.

       -g <gateway>
	      Specify  the  hostname of the gateway through which to route packets.  This is required whenever the destination host isn't directly
	      attached to the same network as the host from which you're sending.

       -m <MTU>
	      Specify the MTU to be used when sending out packets.  This option allows you to set a fake MTU, allowing the simulation  of  network
	      interfaces with small MTU's without setting them so.

       -p <test>
	      Run a...

SEE ALSO

       ipresend(1), ipsend(1), bpf(4), ipsend(5)

DIAGNOSTICS

       Only one of the numeric test options may be given when iptest is run.

       Needs to be run as root.

BUGS

       If you find any, please send email to me at darrenr@pobox.com

																	 IPTEST(1)