|
|
Sponsored Content
Top Forums
UNIX for Dummies Questions & Answers
crontab not working right
Post 38227 by thehoghunter on Wednesday 9th of July 2003 02:39:14 PM
07-09-2003
|
|
10 More Discussions You Might Find Interesting
1. 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
2. UNIX for Advanced & Expert Users
Dear all
We have SunOS 5.10 Generic_127127-11 sun4u sparc SUNW,Sun-Fire-V250
i have scheduled cronjob but its not working
Crontab details
15 15 * * * /d5/oratest/testdb/hotbackup_new.sh TEST247
15 15 * * * mkdir -p rajesh /d4/appltest
Crontab log details
> CMD: mkdir... (4 Replies)
Discussion started by: rajesh_hv
4 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 SUSE
fvwm-bug
fvwm-bug(1) Fvwm Modules fvwm-bug(1) NAME
fvwm-bug - report a bug in fvwm SYNOPSIS
fvwm-bug [--help] [--version] [address] DESCRIPTION
fvwm-bug is a shell script to help the user compose and mail bug reports concerning fvwm in a standard format. fvwm-bug invokes the editor specified by the environment variable EDITOR on a temporary copy of the bug report format outline. The user must fill in the appropriate fields and exit the editor. fvwm-bug then mails the completed report to the local fvwm maintainer, the fvwm workers list fvwm-work- ers@fvwm.org, or address. If the report cannot be mailed, it is saved in the file dead.fvwm-bug in the invoking user's home directory. The bug report format outline consists of several sections. The first section provides information about the machine, operating system, the fvwm version, and the compilation environment. The second section should be filled in with a description of the bug. The third sec- tion should be a description of how to reproduce the bug. The optional fourth section is for a proposed fix. Fixes are encouraged. ENVIRONMENT
fvwm-bug will utilize the following environment variables if they exist: EDITOR Specifies the preferred editor. If EDITOR is not set, fvwm-bug defaults to emacs. HOME Directory in which the failed bug report is saved if the mail fails. Fvwm 7 May 208 (2.5.26) fvwm-bug(1)