Sponsored Content
Full Discussion: crontab NOT working
Top Forums UNIX for Advanced & Expert Users crontab NOT working Post 302090541 by Corona688 on Tuesday 26th of September 2006 10:49:40 AM
Old 09-26-2006
[edit] I shouldn't post when it's this early in the morning. OK. I see what you're code is doing now. What are the permissions on the script file?

Last edited by Corona688; 09-26-2006 at 11:54 AM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

crontab not working right

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

crontab not working

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

crontab is not working.

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

crontab not working

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

crontab is not working!!

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

crontab not working

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

Crontab not working, please help

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

Crontab not working

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

Crontab not working

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

Crontab is not working

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
logjam(1)							    LiveJournal 							 logjam(1)

NAME
logjam - GTK+ client for LiveJournal SYNOPSIS
logjam [OPTIONS] [FILE] DESCRIPTION
logjam is a GTK+ client for LiveJournal-based sites such as livejournal.com. Aside from writing entries, logjam lets you modify your friends list, edit your previous entries, and more. When run with no arguments (or just username option), logjam will run in the GUI mode. The user interface is mostly self-explanatory, and won't be discussed here in detail, except for a few notes below. OPTIONS AND COMMANDS
Options can be given in either short or long forms. For help on a particular commands, type "logjam COMMAND help". For example, "logjam grep help" will supply help about the grep command. Options: -v, --version Show version of program. -q, --quiet Say less. -u, --username=USERNAME Username to operate as. -p, --password=PASSWORD Password for the current user. -a, --postas=USERNAME User/community to post as. -f, --file=FILE File to load. -e, --edit Use default editor to edit post. Subcommands: checkfriends Efficiently check friends list for updates. console Run a command on the LiveJournal console. post Post event immediately. offline Manage offline copies of your journal. user Manage user list. Also, GTK+ command line options (such as --display) can be used. GUI
This section describes some of the GUI features that aren't immediately apparent. Check Friends logjam can monitor your friends list and notify you when new entries are posted there. Enable this by right-clicking on the indicator at the bottom-left corner of the application window and selecting the appropriate menu item. You may also configure logjam to start doing this automatically for you when you login. When new entries are detected, the indicator will turn red to let you know; click it to resume monitoring or double-click it to open your browser on your friends page. Optionally, you can have logjam open a small "floating" indicator which has some useful GUI settings of its own. Owners of large friends lists may prefer to be notified only after they accumulate several new posts. You may set the threshold for this in the Check Friends settings tab. The default is 1, that is, logjam will tell you immediately when it detects new traffic on your friends page. There is a small limit on the maximum threshold allowed, because this feature is only useful with small threshold values. STARTUP
When given a FILE argument, logjam will start up with an existing file as the base for the composed entry. If the filename given is "-", the data will be read from standard input. Several aspects of the entry, such as its subject field and the journal in which to post it to, can be controlled by other options. This is useful in conjunction with the --commandline option, which causes logjam to post an entry without going to GUI mode, allowing completely non-interactive posts. If you do wish to interactively edit the entry, but don't want to load the GUI, use the --edit option. Autosave logjam will periodically save a draft of your currently edited entry in ~/.logjam/draft if you turn on the draft option in the Preferences dialog. This feature is intended for crash recovery, not archiving. If you want to keep a copy of your posts, you should use the Entry > Save As menu option before submitting them. A future version of logjam will support archiving of your journal. Please note that when you exit the client normally, your draft is cleared. It does not "stick" for the next invocation, as in the behavior of some other clients. Checking friends from the command line You can use logjam as a backend for a script or another application that wishes to check the friends view. This may be useful if you don't want to use the GUI, or if you have several journals (in conjunction with --username). To do this, invoke logjam once with --checkfriends=purge (-rpurge if you're using short options), and then something like: logjam --checkfriends && new-entries-handler Make sure that your script or application purges the checkfriends status as described above once the user has acknowledged the new items, otherwise logjam will always report there's nothing new. You should also pay attention to limiting your query rate, despite the fact that logjam will refuse to flood the server with queries. For more information, see the messages on the command line. (To suppress these messages, use --quiet.) SEE ALSO
<http://logjam.danga.com> <http://www.livejournal.com/users/logjam/> <http://www.livejournal.com> AUTHOR
This manual page was mostly written by Gaal Yahas <gaal@forum2.org>. 4.1.1 2003-04-25 logjam(1)
All times are GMT -4. The time now is 01:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy