What happens when you manually call uuencode and mailx and send some dummy file to your account?
Check if your /tmp still has following permissions:
Or if the script is called from another user (cron?) than before?
Hi,
We have a apps database running on HP-UX 11.11. Yesterday, we had a problem with the server which was resolved after rebooting the server. Now the problem I am facing is that now the files created by application manager user has weird file permissions. Like instead of rw-r-r it is... (1 Reply)
one of the business users is ftping files into unix box using user name ftp_user, where as i am using infa_user to login into same unix box. When i am trying to access those or copy over those files from upload directory it says permission denied.
Though i know the password of ftp_user to... (4 Replies)
one of the business users is ftping files into unix box using user name ftp_user, where as i am using infa_user to login into same unix box. When i am trying to access those or copy over those files from upload directory it says permission denied.
Though i know the password of... (4 Replies)
Hi,
I am sending mail inside my script based on various conditions.
Here is the problem,
when there are more than one condion at a time, the mailx adds the messages into one ( at the time of the second mail)
example:
inner_fn ()
{
if ; then
echo "inner function mail" | mailx... (3 Replies)
Hi everybody,
following is the scenario;
OS HP UX 11.23
two users:
# id bodi
uid=109(bodi) gid=20(users) groups=1(other),2(bin),3(sys),106(oinstall)
# id ossmed
uid=121(ossmed) gid=20(users)
umask
077
directory name /home/mydir
directory permissions drwxrwxrwx
requirement: to... (3 Replies)
Hi guys
I am trying to send an email using mailx function and want the message body to appear on different lines.
My code is :
WT=`echo "Tapes are : $x Holder are : $y" `
echo $WT|mailx -s "Alert" xyx@abc.com
I want to receive the email like this:
Tapes are :2
Holders are... (2 Replies)
Hello,
I have a file temp.txt with the below contents :
Sep 9 03:04:51 adcsdp01 MAPDR2_00: Unable to open trace file adpstartarv.log. (Error 110 Resource temporarily unavailable)
Sep 9 03:05:35 adcsdp01 MAPDR2_00: SAP Service ADPMR2_00 successfully started.
Sep 9 03:04:51 adcsdp01... (7 Replies)
Hi All,
Im facing a problem with sending tar file via mailx command. Your help would be much appreciated.
Im trying to tar a set of CSV files in a folder using the below command
tar cvf Report.tar.gz *_03172016.CSV
and sending this tar file using mailx command as mentioned below
... (2 Replies)
Hi,
I am trying to send an email using mailx command in Linux terminal. Though I give invalid address it is giving response as Recipient ok and sent message. My command is here. Not sure what is wrong. Can anyone please assist?
echo -e 'New User'| mailx -v -s 'New User' y@gggg.com
... (1 Reply)
Hello,
I am facing an issue with email in Linux. I am using mailx command to send email.
When I give invalid domain address then it is taking both sender and recipient as sender email and trying to send email.
Below is my command
echo -e "${EMAIL_TEXT}" | mailx -v -s "${SUBJECT}" -r... (5 Replies)
Discussion started by: yuvi
5 Replies
LEARN ABOUT OPENDARWIN
cron
cron(1M) System Administration Commands cron(1M)NAME
cron - clock daemon
SYNOPSIS
/usr/sbin/cron
DESCRIPTION
cron starts a process that executes commands at specified dates and times.
You can specify regularly scheduled commands to cron according to instructions found in crontab files in the directory
/var/spool/cron/crontabs. Users can submit their own crontab file using the crontab(1) command. Commands which are to be executed only once
can be submitted using the at(1) command.
cron only examines crontab or at command files during its own process initialization phase and when the crontab or at command is run. This
reduces the overhead of checking for new or changed files at regularly scheduled intervals.
As cron never exits, it should be executed only once. This is done routinely by way of the svc:/system/cron:default service. The file
/etc/cron.d/FIFO file is used as a lock file to prevent the execution of more than one instance of cron.
cron captures the output of the job's stdout and stderr streams, and, if it is not empty, mails the output to the user. If the job does not
produce output, no mail is sent to the user. An exception is if the job is an at(1) job and the -m option was specified when the job was
submitted.
cron and at jobs are not executed if your account is locked. Jobs and processses execute. The shadow(4) file defines which accounts are not
locked and will have their jobs and processes executed.
Setting cron Jobs Across Timezones
The timezone of the cron daemon sets the system-wide timezone for cron entries. This, in turn, is by set by default system-wide using
/etc/default/init.
If some form of daylight savings or summer/winter time is in effect, then jobs scheduled during the switchover period could be executed
once, twice, or not at all.
Setting cron Defaults
To keep a log of all actions taken by cron, you must specify CRONLOG=YES in the /etc/default/cron file. If you specify CRONLOG=NO, no log-
ging is done. Keeping the log is a user configurable option since cron usually creates huge log files.
You can specify the PATH for user cron jobs by using PATH= in /etc/default/cron. You can set the PATH for root cron jobs using SUPATH= in
/etc/default/cron. Carefully consider the security implications of setting PATH and SUPATH.
Example /etc/default/cron file:
CRONLOG=YES
PATH=/usr/bin:/usr/ucb:
This example enables logging and sets the default PATH used by non-root jobs to /usr/bin:/usr/ucb:. Root jobs continue to use
/usr/sbin:/usr/bin.
The cron log file is periodically rotated by logadm(1M).
FILES
/etc/cron.d Main cron directory
/etc/cron.d/FIFO Lock file
/etc/default/cron cron default settings file
/var/cron/log cron history information
/var/spool/cron Spool area
/etc/cron.d/queuedefs Queue description file for at, batch, and cron
/etc/logadm.conf Configuration file for logadm
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO svcs(1), at(1), crontab(1), sh(1), logadm(1M), svcadm(1M), queuedefs(4), shadow(4), attributes(5), smf(5)NOTES
The cron service is managed by the service management facility, smf(5), under the service identifier:
svc:/system/cron:default
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
DIAGNOSTICS
A history of all actions taken by cron is stored in /var/cron/log and possibly in /var/cron/olog.
SunOS 5.10 5 Aug 2004 cron(1M)