07-12-2012
If you have sample email from when the backup worked, check the real source address of the email (look at the email headers with your email reader) and also look for clues in the mail body.
If you still have the server mail logs going back to when it worked, check whether the destination email address ever appeared in the mail log.
If other backups still work, look at how they are configured.
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
Please I need your expert advise on how to prevent/lock from execution job1 while job2 is still running in Unix... THanks:) (3 Replies)
Discussion started by: tikang
3 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I performed backup on tape and I want to append more files to my previous backup on the same backup tape. But before I do that I need to know the backup file size of the first backup I performed so that I know the available size on the backup tape. Can someone help me what command I will use... (0 Replies)
Discussion started by: ayhanne
0 Replies
3. SCO
I am trying to make a full backup of my system using the cpio command. The Tape Unit is a SCSI DDS.
The process started fine but after about 30 minutes, it just stopped and showed the following message:
1755 Signal 31 - Core dumped
Any idea of what is causing this and how to fix it?
... (4 Replies)
Discussion started by: zionpc
4 Replies
4. Solaris
Hi,
i have a script which need to do behave differently when run as a startup process from init.d/ rc2.d script and when run manually from shell.
How do i distinguish whether my script is run by init process or by shell??
Will the command
/proc/$$/psinfo | grep "myscript" work well???... (2 Replies)
Discussion started by: vickylife
2 Replies
5. UNIX for Advanced & Expert Users
I am trying to backup my .bash_history and I want to keep every version of the backup. I am thinking to put one of these in my crontab.
0 0 * * 0,3 cat .bash_history > boo
0 0 * * 0,3 cp .bash_history boo
I would like the backups to be called boo1, boo2, boo3, etc. I would like to keep... (7 Replies)
Discussion started by: cokedude
7 Replies
6. Shell Programming and Scripting
Hi Everyone,
we are running rsync with --backup mode, Are there any rsync options to remove backup folders on successful deployment?
Thanks in adv. (0 Replies)
Discussion started by: MVEERA
0 Replies
7. Shell Programming and Scripting
Hello everyone,
I have 2 questions :
1) I have a backup shell script, let's call it backup.sh, that is called every hour as a cron job.
As a matter of fact a backup could last more than one hour.
It mounts a NAS and then do some rsync on important directories, so really I don't want to... (2 Replies)
Discussion started by: freddie50
2 Replies
8. Shell Programming and Scripting
HI all, im new to shell scripting. need your guidence for my script. i wrote one script and is attached here
Im explaining the requirement of script.
AIM: Shell script to run automatically as per scheduled and backup few network devices configurations. Script will contain a set of commands... (4 Replies)
Discussion started by: saichand1985
4 Replies
9. Shell Programming and Scripting
I am trying a cron on root user to backup to tape using TAR command
here is the cron entry
11 08 * * 6 /erdhot1cron 2>&1 >> /test3/scripts/dba/erdhot1cron.log
here is script inside - edhot1cron
#!/bin/bash
vsysdt=`date +%d%m%y`
date
tar -cvf /dev/st0... (4 Replies)
Discussion started by: vijaymec50
4 Replies
LEARN ABOUT CENTOS
xdg-email
XDG-EMAIL(1) xdg-email Manual 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/wiki/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 manual page.
--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/wiki/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'
AUTHORS
Kevin Krammer
Author.
Jeremy White
Author.
COPYRIGHT
Copyright (C) 2006
xdg-utils 1.0 06/10/2014 XDG-EMAIL(1)