10-15-2011
Quote:
Originally Posted by
ctsgnb
why do you use " | tee " ???
I figured the script would still need access to STDOUT given that it acts based upon the output. As I mentioned though, that was only done after the script was found to not work.
Quote:
By the way i am not very familiar with the notation you use in your cronjob definition, so i don't know if it makes sens as is.
That notation is not supported in all flavors of UNIX but Linux is more than happy with it.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi All
Some how, variables are not getting exported while running the script in cronjob. Variable value is coming blank. But the variables are geting the value when the same script I am running manually. Any idea why?
When running the script in cron-job
==================================... (7 Replies)
Discussion started by: csaha
7 Replies
2. Shell Programming and Scripting
Hi
I have a shell script, it run ok if executed from the path it is located at but doesnot run when the same is tried through cron-job.
can someone help me please.
regards
gaurav shrinivas
Email address removed (8 Replies)
Discussion started by: gauravshrinivas
8 Replies
3. Shell Programming and Scripting
Hi all, i got a really strange problem
i wrote a script, when i run this script manually everything works fine
but when i make a cronjob for it, with the same user, the EXPECT script will not work.
Only the first line will be executed
this is the SHell bash script
#!/bin/sh;
php -q... (2 Replies)
Discussion started by: digitac
2 Replies
4. Shell Programming and Scripting
Hi
Im very new at working with unix and this problem I simply can not understand. I know there are a lot of threads about problems with shell scripts behaving differently when run from a terminal and from a cronjob. I have tried everything(almost) but I still havent cracked this problem.
Im... (15 Replies)
Discussion started by: Nightowl
15 Replies
5. Shell Programming and Scripting
I have a very basic perl script that attempts to find if a process is running. If the process is not running then the script is supposed to start the process. If I execute the script from command line it works fine as expected. However if the script is executed via cronjob, the script cannot find... (1 Reply)
Discussion started by: ypant
1 Replies
6. UNIX for Dummies Questions & Answers
Hey all
Found this forum googling for solutions. Great community this!
Im looking for help trying to run a php script every 20 minutes.
The script basically has to loop continuously forever but inexplicably hangs every 30 minutes or so. I have not been able to debug the script and find... (2 Replies)
Discussion started by: aras
2 Replies
7. Shell Programming and Scripting
Hi,
I have script which is properly running but when i schedule it in cron it throws an error like :
Your "cron" job on retrprdapp1
/usr/bin/sh /retr/cron/ftp.sh 2>&1
produced the following output:
/retr/cron/ftp.sh: syntax error at line 17: `(' unexpected
line17 is
# Get list of... (10 Replies)
Discussion started by: rajagasti
10 Replies
8. UNIX for Dummies Questions & Answers
hi everyone I'm newbie in this forum hope I can get some help here :)
I have a command in crontab that executed every 1 minute
sometime this command need more than 1 minute to finish
the problem is, the crontab execute this command although it's not finish processing yet and causing the system... (7 Replies)
Discussion started by: 2j4h
7 Replies
9. UNIX for Dummies Questions & Answers
Hi,
I have a .ksh script which updates the database. The script is running fine manually but it is not running through cron.All the file permissions are fine.
The script contents are as below:
#!/usr/bin/ksh
ddate=`date +%Y%m%d`
echo $ddate
nohup sqlplus crm/crm @db_state_sync.sql >>... (3 Replies)
Discussion started by: shivangi
3 Replies
10. Shell Programming and Scripting
hi, please help, keep getting this bolded error and look it up and people say
its your environment variable though i tried to set it manually in expect..it run fine if i run it manually but once i run it by cronjob it error below..i tried to comment out ip/login info with *..
logfile::
START... (0 Replies)
Discussion started by: cssanangeles
0 Replies
LEARN ABOUT LINUX
update-motd
update-motd(5) File Formats Manual update-motd(5)
NAME
update-motd - dynamic MOTD generation
SYNOPSIS
/etc/update-motd.d/*
DESCRIPTION
UNIX/Linux system adminstrators often communicate important information to console and remote users by maintaining text in the file
/etc/motd, which is displayed by the pam_motd(8) module on interactive shell logins.
Traditionally, this file is static text, typically installed by the distribution and only updated on release upgrades, or overwritten by
the local administrator with pertinent information.
Ubuntu introduced the update-motd framework, by which the motd(5) is dynamically assembled from a collection of scripts at login.
Executable scripts in /etc/update-motd.d/* are executed by pam_motd(8) as the root user at each login, and this information is concatenated
in /var/run/motd. The order of script execution is determined by the run-parts(8) --lsbsysinit option (basically alphabetical order, with
a few caveats).
On Ubuntu systems, /etc/motd is typically a symbolic link to /var/run/motd.
BEST PRACTICES
MOTD fragments must be scripts in /etc/update-motd.d, must be executable, and must emit information on standard out.
Scripts should be named named NN-xxxxxx where NN is a two digit number indicating their position in the MOTD, and xxxxxx is an appropriate
name for the script.
Scripts must not have filename extensions, per run-parts(8) --lsbsysinit instructions.
Packages should add scripts directly into /etc/update-motd.d, rather than symlinks to other scripts, such that administrators can modify or
remove these scripts and upgrades will not wipe the local changes. Consider using a simple shell script that simply calls exec on the
external utility.
Long running operations (such as network calls) or resource intensive scripts should cache output, and only update that output if it is
deemed expired. For instance:
/etc/update-motd.d/50-news
#!/bin/sh
out=/var/run/foo
script="w3m -dump http://news.google.com/"
if [ -f "$out" ]; then
# Output exists, print it
echo
cat "$out"
# See if it's expired, and background update
lastrun=$(stat -c %Y "$out") || lastrun=0
expiration=$(expr $lastrun + 86400)
if [ $(date +%s) -ge $expiration ]; then
$script > "$out" &
fi
else
# No cache at all, so update in the background
$script > "$out" &
fi
Scripts should emit a blank line before output, and end with a newline character. For instance:
/etc/update-motd/05-lsb-release
#!/bin/sh
echo
lsb-release -a
FILES
/etc/motd, /var/run/motd, /etc/update-motd.d
SEE ALSO
motd(5), pam_motd(8), run-parts(8)
AUTHOR
This manpage and the update-motd framework was written by Dustin Kirkland <kirkland@canonical.com> for Ubuntu systems (but may be used by
others). Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version
3 published by the Free Software Foundation.
On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL.
update-motd 13 April 2010 update-motd(5)