04-10-2008
And check your mail; usually you get an email with the output from a command if it generated any (such as when there was an error, with any decently implemented command).
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am running a script by scheduling it using the cron. The line in the cron file is -
10 * * * * ksh -v /apps/gofis/svam/cos_automation/cos_automation.sh vpqa > /apps/gofis/svam/cos_automation/cron.log 2>&1
But after the job is executed, the cron.log contains some part from... (4 Replies)
Discussion started by: ankurgupta
4 Replies
2. UNIX for Advanced & Expert Users
I have written a shell script and when i run it from shell prompt it runs fine but in the cron it only runs partially.
That means cron is working fine.
there is a command which i am using in the script which doesn't run at all.
That comman uses different user privileges like ptadmin
i am not... (4 Replies)
Discussion started by: ajnabi
4 Replies
3. HP-UX
Hi,
I have a cron schedule like this
04,16,28,40,52 * * * * /nag/startProcessABatch (unix script)
i want to add new lines in this file (like Logging), i just copy this file into a /tmp folder (for backup copy), and i have edited this file (added few lines of code for logging).
... (1 Reply)
Discussion started by: nag_sundaram
1 Replies
4. UNIX for Dummies Questions & Answers
I would like to add a job using cron. I have following questions
- cron jobs are launched using what login-id
e.g. is the script launced using my login-id
- In which directory would the cron jobs be launched ?
- where do the environment variables required in the script being lauched come... (3 Replies)
Discussion started by: sharanbr
3 Replies
5. UNIX for Dummies Questions & Answers
I have some cron jobs that are taking a might long time. That is because they are screen scrapers and I inserted an extra long pause (10 minutes between screens) to be extra polite and minimize network traffic. I was going to have them run once a day but now I'm thinking once a week.
How do I... (2 Replies)
Discussion started by: siegfried
2 Replies
6. Shell Programming and Scripting
i have a simple script that ftp a file out, manually running it works fine.
#!/bin/sh
ftp 152.226.69.48 << cmd
bin
get applicant_vw.txt
quit
cmd
but when I cron it,
14 9 * * * /opt/home/XXX/XXX/dailyjob.sh > /opt/home/XXX/XXX/cronlog.txt
seems that it was executed because i can... (2 Replies)
Discussion started by: beisaikong
2 Replies
7. Solaris
Folks,
I have a solaris 10 system.
I am having trouble with cron to run a dialog command.
When I simply execute below using a cron it does not work.
I am new to the forum, please help me to understand it better.
Thanks in advance.
#!/bin/sh
dialog --infobox "Please wait " 10 10 (2 Replies)
Discussion started by: wndgs
2 Replies
8. Solaris
Hi,
I''ve made a script that's running fine from the command line but when running from cron it encounters the following issue:
/tmp/tstscript/testfail.ksh: typeset: not found
I've searched in Google and couldn't find anything, here's the beggining of the script (I can post the rest if... (4 Replies)
Discussion started by: Cvg
4 Replies
9. Shell Programming and Scripting
How to check what cron is scheduled to run? I don't want to modify anything. Thanks (1 Reply)
Discussion started by: stevensw
1 Replies
10. Solaris
Hi ,
I have removed a cron for particular user , but cron job seems to be running even after the cron entry is removed. The purpose of the cron was to sendmail to user ( it uses mailx utility )
I have restarted cron and sendmail service still user is getting mail alerts from the cron job. And... (4 Replies)
Discussion started by: chidori
4 Replies
LEARN ABOUT OPENSOLARIS
xdg-email
XDG-EMAIL(1) XDG-EMAIL(1)
NAME
xdg-email - command line tool for sending mail using the user's preferred e-mail composer
SYNOPSIS
xdg-email [--utf8] [--cc address] [--bcc address] [--subject text] [--body text] [--attach file] [mailto-uri address(es)]
xdg-email {--help --manual --version}
DESCRIPTION
xdg-email opens the user's preferred e-mail composer in order to send a mail to address(es) or mailto-uri. RFC2368 defines mailto: URIs.
xdg-email limits support to, cc, subject and body fields in mailto-uri, all other fields are silently ignored. address(es) must follow the
syntax of RFC822. Multiple addresses may be provided as separate arguments.
All information provided on the command line is used to prefill corresponding fields in the user's e-mail composer. The user will have the
opportunity to change any of this information before actually sending the e-mail.
xdg-email is for use inside a desktop session only. It is not recommended to use xdg-email as root.
See http://portland.freedesktop.org/EmailConfig for information on how the user can change the e-mail composer that is used.
OPTIONS
--utf8 Indicates that all command line options that follow are in utf8. Without this option, command line options are expected to be
encoded according to locale. If the locale already specifies utf8 this option has no effect. This option does not affect mailto URIs
that are passed on the command line.
--cc address
Specify a recipient to be copied on the e-mail.
--bcc address
Specify a recipient to be blindly copied on the e-mail.
--subject text
Specify a subject for the e-mail.
--body text
Specify a body for the e-mail. Since the user will be able to make changes before actually sending the e-mail, this can be used to
provide the user with a template for the e-mail. text may contain linebreaks.
--attach file
Specify an attachment for the e-mail. file must point to an existing file.
Some e-mail applications require the file to remain present after xdg-email returns.
--help Show command synopsis.
--manual
Show this manualpage.
--version
Show the xdg-utils version information.
ENVIRONMENT VARIABLES
xdg-email honours the following environment variables:
XDG_UTILS_DEBUG_LEVEL
Setting this environment variable to a non-zero numerical value makes xdg-email do more verbose reporting on stderr. Setting a
higher value increases the verbosity.
EXIT CODES
An exit code of 0 indicates success while a non-zero exit code indicates failure. The following failure codes can be returned:
1 Error in command line syntax.
2 One of the files passed on the command line did not exist.
3 A required tool could not be found.
4 The action failed.
5 No permission to read one of the files passed on the command line.
CONFIGURATION
Visit http://portland.freedesktop.org/EmailConfig for information how to configure xdg-email to use the email client of your choice.
EXAMPLES
xdg-email 'Jeremy White <jwhite@example.com>'
xdg-email --attach /tmp/logo.png
--subject 'Logo contest'
--body 'Attached you find the logo for the contest.'
'jwhite@example.com'
xdg-email --subject 'Your password is about to expire'
'jwhite@example.com' 'bastian@example.com' 'whipple@example.com'
AUTHOR
Kevin Krammer, Jeremy White.
<kevin.krammer@gmx.at>
<jwhite@codeweavers.com>
xdg-utils 1.0 06/24/2007 XDG-EMAIL(1)