09-20-2008
Strange error on mpack from cronjob
I have a shell script which mails a file. It runs fine when executed at prompt, but from cronjob the following line gives an error:
HTML Code:
$ /opt/local/bin/mpack -s "TTW posts " $FILEPATH/ttw.html myemail@gmail.com
Error is : (some junk chars) followed by
No such file or directory.
Before this line ,I have `
head`ed the file to ensure it is found by cron - IT IS. I have also `
which`ed mpack and it (cron) gives the full path. So I am stumped as to why it should fail from cron. Both file and executable are found!
Strangely, after this I also
'links -dump' the file and use mail to mail it to my localhost. Links is also in /opt/local and this line works fine. However, since the stock '
mail' program cannot send an attach, therefore I needed to use mpack.
Doing
'ls -l' on mpack shows it is readable and executable by all -- same as other commands in /opt.
Last edited by sentinel; 09-21-2008 at 04:59 AM..
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
When I give the following
$ ps -ef | grep `echo $var1` | grep -v "grep `echo $var1`" | awk '{print $3}' | grep -v `echo $var1
80892
But when I give the following (made as command substitution) , I get error
$var2=`ps -ef | grep `echo $var1` |... (2 Replies)
Discussion started by: preetikate
2 Replies
2. UNIX for Dummies Questions & Answers
Hi all,
i executed a script.
cat <filename> | grep <pattern> | awk '{print $1}' | read a
i get the answer when i execute it in the shell env (no problem with that)
as
./<name>.ksh
when i tried the same in cron (as an entry in cron)
value is not being read in the variable a through... (1 Reply)
Discussion started by: matrixmadhan
1 Replies
3. Shell Programming and Scripting
Part of my script throws an error.
Your "cron" job on mitv-t-voms02
/usr/tlrscr/runhc.sh
produced the following output:
/usr/tlrscr/runhc.sh: top: not found
/usr/tlrscr/runhc.sh: top: not found
/usr/tlrscr/runhc.sh: top: not found
syntax error on line 1, teletype
That part of... (2 Replies)
Discussion started by: sundar63
2 Replies
4. Shell Programming and Scripting
Hi,
I was using mpack to send mails using cronjob with attachments. It was working perfect. But recently it's behaving strangely. Its sending the mails without any error message but the mail is not getting delivered.
The code I was using:
/usr/local/bin/mpack -s "$SUBJECT" -d $MSGBODY... (0 Replies)
Discussion started by: itesh.dash
0 Replies
5. UNIX for Dummies Questions & Answers
Hi all,
I was using mpack for sending mails with pdf as attachment. It was working well. but some days back my server was shut down forcefully due to power failure and I found now the mails are moving to the queue always.
I checked in /var/spool/mail/mqueue. Is the forece shutdown has to do... (0 Replies)
Discussion started by: itesh.dash
0 Replies
6. 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
7. Shell Programming and Scripting
Hello,
I'm trying to implement a script to call a third-party tool every so often and write the results to a file. If I run it interactively it works fine, but when it comes to run it out of a cronjob, I keep getting this error:
stty: tcgetattr: a specified file does not support the... (3 Replies)
Discussion started by: fabiogilr
3 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. Shell Programming and Scripting
Hi All ,
Please read the below data carefully.
I have run the below script on unix server its running succesfully. but when i run the same script using cronsetyp it giving me the error :
command not found at (line num):cruiseStartup.sh
below is code
netstat -anp |grep 8181... (5 Replies)
Discussion started by: aish11
5 Replies
10. UNIX for Dummies Questions & Answers
I am receiving an error when i type the command dmesg
sudo: sysmon : pam_authenticate: Conversation failure ; TTY=unknown ; PWD=/export/home/sysmon ; USER=root ; COMMAND=/opt/scripts/cronmgmt/synch_crontab.ksh
Whats it about and how can I remove it ? (1 Reply)
Discussion started by: Junaid Subhani
1 Replies
tclsh(1) Tcl Applications tclsh(1)
__________________________________________________________________________________________________________________________________________________
NAME
tclsh - Simple shell containing Tcl interpreter
SYNOPSIS
tclsh ?fileName arg arg ...?
_________________________________________________________________
DESCRIPTION
Tclsh is a shell-like application that reads Tcl commands from its standard input or from a file and evaluates them. If invoked with no
arguments then it runs interactively, reading Tcl commands from standard input and printing command results and error messages to standard
output. It runs until the exit command is invoked or until it reaches end-of-file on its standard input. If there exists a file .tclshrc
(or tclshrc.tcl on the Windows platforms) in the home directory of the user, tclsh evaluates the file as a Tcl script just before reading
the first command from standard input.
SCRIPT FILES
If tclsh is invoked with arguments then the first argument is the name of a script file and any additional arguments are made available to
the script as variables (see below). Instead of reading commands from standard input tclsh will read Tcl commands from the named file;
tclsh will exit when it reaches the end of the file. There is no automatic evaluation of .tclshrc in this case, but the script file can
always source it if desired.
If you create a Tcl script in a file whose first line is
#!/usr/local/bin/tclsh
then you can invoke the script file directly from your shell if you mark the file as executable. This assumes that tclsh has been
installed in the default location in /usr/local/bin; if it's installed somewhere else then you'll have to modify the above line to match.
Many UNIX systems do not allow the #! line to exceed about 30 characters in length, so be sure that the tclsh executable can be accessed
with a short file name.
An even better approach is to start your script files with the following three lines:
#!/bin/sh
# the next line restarts using tclsh
exec tclsh "$0" "$@"
This approach has three advantages over the approach in the previous paragraph. First, the location of the tclsh binary doesn't have to be
hard-wired into the script: it can be anywhere in your shell search path. Second, it gets around the 30-character file name limit in the
previous approach. Third, this approach will work even if tclsh is itself a shell script (this is done on some systems in order to handle
multiple architectures or operating systems: the tclsh script selects one of several binaries to run). The three lines cause both sh and
tclsh to process the script, but the exec is only executed by sh. sh processes the script first; it treats the second line as a comment
and executes the third line. The exec statement cause the shell to stop processing and instead to start up tclsh to reprocess the entire
script. When tclsh starts up, it treats all three lines as comments, since the backslash at the end of the second line causes the third
line to be treated as part of the comment on the second line.
You should note that it is also common practise to install tclsh with its version number as part of the name. This has the advantage of |
allowing multiple versions of Tcl to exist on the same system at once, but also the disadvantage of making it harder to write scripts that |
start up uniformly across different versions of Tcl.
VARIABLES
Tclsh sets the following Tcl variables:
argc Contains a count of the number of arg arguments (0 if none), not including the name of the script file.
argv Contains a Tcl list whose elements are the arg arguments, in order, or an empty string if there are no arg arguments.
argv0 Contains fileName if it was specified. Otherwise, contains the name by which tclsh was invoked.
tcl_interactive
Contains 1 if tclsh is running interactively (no fileName was specified and standard input is a terminal-like device), 0
otherwise.
PROMPTS
When tclsh is invoked interactively it normally prompts for each command with ``% ''. You can change the prompt by setting the variables
tcl_prompt1 and tcl_prompt2. If variable tcl_prompt1 exists then it must consist of a Tcl script to output a prompt; instead of out-
putting a prompt tclsh will evaluate the script in tcl_prompt1. The variable tcl_prompt2 is used in a similar way when a newline is typed
but the current command isn't yet complete; if tcl_prompt2 isn't set then no prompt is output for incomplete commands.
KEYWORDS
argument, interpreter, prompt, script file, shell
Tcl tclsh(1)