Recently i started using sendmail instead of mutt to send the email .
In one script i have both sendmail and mutt included and they both give different emails.
when i run the above script manually i get the both emails , but when i cron it i get only second email ie email from mutt and not the sendmail.
anything being missed or anything specific needs to be set for sendmail to work from cron.
also how to attach file in sendmail.
both did not work for me.
Hi,
I can use 'crontabs –e' and do all the scheduling I like. However I would like to auto send myself just the cronjobs logs that fail. That is to say the PIDs that fail and the related lines with those PID’s only. (Not the full set of logs) Has anyone done this work? Or does an AIX 5.3 tool... (0 Replies)
I run cron in solaris 10 zone. One cron job which syncing files to nfs mounted on container, creates after finishing another cron proccess(/usr/sbin/cron), and after 100 existing cron proccesses next cron job will not start. It's too weird for me, I'm not able to solve this problem. Theoretically... (3 Replies)
Hello All,
Anybody please help me to know ,what happens when a user having entry in both cron.allow and cron.deny files.Wheather the user will be able to access the crontab???
Thanks in advance
Vaisakh (5 Replies)
Hi, all!
I was working on my Debian, minding my own business but then I wanted to see what happened if the same user was included on both cron.allow and cron.deny :p
I would have bet that cron.deny was going to override cron.allow for security reasons, but my computer proved me wrong:... (3 Replies)
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)
I am running SCO 5.0.6 and using sendmail 8.11.0 and having issues with smtp authentication. When trying to send mail the following message will kick back.
(reason: 530 5.7.1 Authentication required)
530 5.7.1 Authentication required
Not sure what needs to be tweeked in sendmail.cf but I... (1 Reply)
Hi,
1)
If some job supposed to run on 1st of every month at 7 AM
In cron job when we have a blackout on the 1st ( i.e when 1st falls on a sunday ) how can we make the job run the next business day?
2) How can we run a job on 25th of every quarter 7 AM(jan,apr,jul,oct)
And if 25th... (5 Replies)
Hello gurus,
I am making what I think is a simple db2 call from within a shell script but I am having difficulty producing the desired
report when I run the script shown below from a shell script in cron. For example, my script and the crontab file setup
is shown below:
#!/bin/ksh
db2... (3 Replies)
Hi all,
I have read about sendmail running as 2 separate process.
1 as a MSP, and the other as the real daemon or MTA.
In my current configuration,
the sendmail-client is disabled.
Both submit.cf and sendmail.cf are left as default untouch
I do not specified any mailhost... (3 Replies)
Discussion started by: javanoob
3 Replies
LEARN ABOUT HPUX
nmudiff
NMUDIFF(1) General Commands Manual NMUDIFF(1)NAME
nmudiff - email an NMU diff to the Debian BTS
SYNOPSIS
nmudiff [options]
DESCRIPTION
nmudiff should be run in the source tree of the package being NMUed, after the NMU is built. It assumes that the source packages (specifi-
cally, the .dsc and any corresponding tar and diff files) for both the previous version of the package and the newly built NMU version are
in the parent directory. It then uses debdiff to generate a diff between the previous version and the current NMU, and either runs mutt or
an editor (using sensible-editor) so that the mail message (including the diff) can be examined and modified; once you exit the editor the
diff will be mailed to the Debian BTS.
The default behaviour is that if exactly one bug is closed by this NMU, then that bug will be mailed, otherwise a new bug will be submit-
ted. This behaviour may be changed by command line options and configuration file options.
OPTIONS --new Instead of mailing the bug reports which are to be closed by this NMU, a new bug report is submitted directly to the BTS.
--old Send the bug report to all of the bugs which are being closed by this NMU, rather than opening a new bug report. This option has no
effect if no bugs are being closed by this NMU.
--mutt Use mutt(1) for editing and sending the message to the BTS (default behaviour). This can be controlled using a configuration file
option (see below).
--no-mutt
Use sensible-editor(1) to edit the message and then mail it directly using /usr/bin/sendmail. This can be controlled using a con-
figuration file option (see below).
--sendmail SENDMAILCMD
Specify the sendmail command. The command will be split on white space and will be interpreted by the shell. Default is
/usr/sbin/sendmail. The -t option will be automatically added if the command is /usr/sbin/sendmail or /usr/sbin/exim*. For other
mailers, if they require a -t option, this must be included in the SENDMAILCMD, for example: --sendmail="/usr/sbin/mymailer -t".
This can also be set using the devscripts configuration files; see below.
--from EMAIL
If using the sendmail (--no-mutt) option, then the email to the BTS will be sent using the name and address in the environment vari-
ables DEBEMAIL and DEBFULLNAME. If these are not set, then the variables EMAIL and NAME will be used instead. These can be over-
ridden using the --from option. The program will not work in this case if an email address cannot be determined.
--delay DELAY
Indicate in the generated mail that the NMU has been uploaded to the DELAYED queue, with a delay of DELAY days. The default value
is XX which adds a placeholder to the e-mail. A value of 0 indicates that the upload has not been delayed. This can also be set
using the devscripts configuration files; see below.
--no-delay, --nodelay
Equivalent to --delay 0.
--no-conf, --noconf
Do not read any configuration files. This can only be used as the first option given on the command-line.
--help Display a help message and exit successfully.
--version
Display version and copyright information and exit successfully.
CONFIGURATION VARIABLES
The two configuration files /etc/devscripts.conf and ~/.devscripts are sourced in that order to set configuration variables. Command line
options can be used to override configuration file settings. Environment variable settings are ignored for this purpose. The currently
recognised variables are:
NMUDIFF_DELAY
If this is set to a number, e-mails generated by nmudiff will by default mention an upload to the DELAYED queue, delayed for the
specified number of days. The value 0 indicates that the DELAYED queue has not been used.
NMUDIFF_MUTT
Can be yes (default) or no, and specifies whether to use mutt to compose and send the message or not, as described above.
NMUDIFF_NEWREPORT
This option controls whether a new bug report is made, or whether the diff is sent to the bugs closed by this NMU. Can be maybe
(default), which sends to the existing bug reports if exactly one bug is being closed; yes, which always creates a new report, or
no, which always sends to the reports of the bugs being closed (unless no bugs are being closed, in which case a new report is
always made).
BTS_SENDMAIL_COMMAND
If this is set, specifies a sendmail command to use instead of /usr/sbin/sendmail. Same as the --sendmail command line option.
SEE ALSO debdiff(1), sensible-editor(1) and devscripts.conf(5).
AUTHOR
nmudiff was written and is copyright 2006 by Steinar H. Gunderson and modified by Julian Gilbey <jdg@debian.org>. The software may be
freely redistributed under the terms and conditions of the GNU General Public License, version 2.
DEBIAN Debian Utilities NMUDIFF(1)