10-28-2008
The mkdir command looks suspect. The "-p" parameter just tells mkdir to create intermittent directories. As stated the command will create two directories: "rajesh" under root's home directory; and "/d4/appltest" .
In your example both your crons are set for the same time which may give you a problem sequencing the tasks. However the times in your cron log do not match the crontab described.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am having problems with a sparc5 solaris 7 box, when i try to edit cron, (crontab -e as root), it says
$ crontab -e
0
and then nothing, if i enter anything it errors out but does accept q for quit. But doesn't bring up my editor of the cron file. How can I troubleshoot this?
... (3 Replies)
Discussion started by: kymberm
3 Replies
2. UNIX for Advanced & Expert Users
Hi,
I have put the following entry in crontab and it is NOT working
1 * * * * && /mybin/myjob.sh
As today is Sep 26th, Iam using NF-4 to test.
Thanks (2 Replies)
Discussion started by: baanprog
2 Replies
3. Solaris
I have a script which name is sicaklik.sh
It is in the root directory.
I can run manually but I want to run automatically every 3 minutes but it is not working. WHY?
#whoami
root
#crontab -l
#ident "@(#)root 1.21 04/03/23 SMI"
3 * * * * sh ./sicaklik.sh
#ls -l sicaklik*... (6 Replies)
Discussion started by: getrue
6 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I had setup crontab to execute my script every day midnight 00:00
Below are the current settings.
crontab -l
0 0 * * * /apps/bin/compress.ksh_moht > /dev/null 2>&1
Should it not work?
I need help fix this? (8 Replies)
Discussion started by: shifahim
8 Replies
5. Red Hat
I can run manually script of ntopdump.sh but crontab can't run this script very five minutes.
# crontab -l
*/3 * * * * root sh /root/ping.sh
*/5 * * * * root sh /root/ntopdump.sh
#
# pwd
/root
# ls -l
total 88
-rwxrwxr-x 1 root root 1645 Jun 14 19:01 anaconda-ks.cfg
drwxrwxr-x 2 root... (14 Replies)
Discussion started by: getrue
14 Replies
6. Solaris
Shell = ksh
Hi all,
I scheduled an automated job on my application server like below,
30 13 * * 1-5 $HOME/my_script.sh
However the script was not executed as expected. Any reason that may cause this to happen? (6 Replies)
Discussion started by: isaacniu
6 Replies
7. UNIX for Advanced & Expert Users
Hi,
When I set the crontab to run every minute, every hour, it works fine.
* * * * * env > /tmp/env.output
However I want to run it every day at 8:00 AM and it does not run.
* 8 * * * env > /tmp/env.output
I ran the 'date' command which says it's 8AM PST and also the 'TZ'... (0 Replies)
Discussion started by: samantha13
0 Replies
8. Linux
Hi,
I know this is a common topic. I'm trying to launch a perl script using a contab -e entry. I've been trying diff options but nothing seems to work:
My cron is running:
UID PID PPID C STIME TTY TIME CMD
root 3755 1 0 Nov27 ? 00:00:00 crond
This... (4 Replies)
Discussion started by: krebe
4 Replies
9. Shell Programming and Scripting
Hi All,
I have a script with deatils as :
$ ls -ld catch_logs.sh
-rwx--x--x 1 muser muser 752 Jun 5 22:36 catch_logs.sh
User crontab looks likes:
$ crontab -l
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
* * * * * /opt/scripts/catch_logs.sh
Now if I run this script... (7 Replies)
Discussion started by: Junaid Subhani
7 Replies
10. Red Hat
Dear Friends,
I have Red Hat Linux Enterprise version 6.3. running SAP and oracle.
I have created one crontab for user orasid to execute one job periodically.
But it is not executing. I have checked crontab service is running.
Please help in the matter.
Regards,
Bhagawati Pandey (5 Replies)
Discussion started by: BPANDEY
5 Replies
LEARN ABOUT FREEBSD
mkdir
MKDIR(1) BSD General Commands Manual MKDIR(1)
NAME
mkdir -- make directories
SYNOPSIS
mkdir [-pv] [-m mode] directory_name ...
DESCRIPTION
The mkdir utility creates the directories named as operands, in the order specified, using mode ``rwxrwxrwx'' (0777) as modified by the cur-
rent umask(2).
The options are as follows:
-m mode Set the file permission bits of the final created directory to the specified mode. The mode argument can be in any of the formats
specified to the chmod(1) command. If a symbolic mode is specified, the operation characters '+' and '-' are interpreted relative
to an initial mode of ``a=rwx''.
-p Create intermediate directories as required. If this option is not specified, the full path prefix of each operand must already
exist. On the other hand, with this option specified, no error will be reported if a directory given as an operand already exists.
Intermediate directories are created with permission bits of ``rwxrwxrwx'' (0777) as modified by the current umask, plus write and
search permission for the owner.
-v Be verbose when creating directories, listing them as they are created.
The user must have write permission in the parent directory.
EXIT STATUS
The mkdir utility exits 0 on success, and >0 if an error occurs.
EXAMPLES
Create a directory named foobar:
$ mkdir foobar
Create a directory named foobar and set its file mode to 700:
$ mkdir -m 700 foobar
Create a directory named cow/horse/monkey, creating any non-existent intermediate directories as necessary:
$ mkdir -p cow/horse/monkey
COMPATIBILITY
The -v option is non-standard and its use in scripts is not recommended.
SEE ALSO
rmdir(1)
STANDARDS
The mkdir utility is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
HISTORY
A mkdir command appeared in Version 1 AT&T UNIX.
BSD
March 15, 2013 BSD