I have a backup script that is suppose to run every night of the week, but it never does, it starts to run. The way I can tell is that the dates on dump_log are changing to when the script runs. If I look in the cron log file is shows
! > root 506342 cr /etc/back_up Fri Aug 5 10:30:00... (2 Replies)
Dear Folks,
i am new to hp-ux, i have a problem scheduling the crontab,
The script is working fine at command prompt, but not working at cron, please find a solution for it ,
here are the logs and my schedule at cron:
log after restarting crontab /var/adm/cron/log
! *** cron started *** ... (11 Replies)
I am adding a piece of code which adds entry in crontab ((in brown color))
\crontab -l > $tmpfile
echo "Removing the cleanProcess entry if it already existed.."
grep -v "cleanProcess.sh" $tmpfile > $newtmpfile
lcnt=`grep -c "cleanProcess.sh" $tmpfile`
echo... (4 Replies)
I have a ksh script which will connect to a database and executes some sql scripts. If i run the ksh script it is working fine. But if i schedule it to run at a perticular time using cron the sql script is not running. The scriptl initially creates a spool file for sql script and then connects and... (12 Replies)
We have configured a script to be run at specific time using crontab.
# crontab -l
15 11 * * * VM_Count_V4.shas per the crontab entry script should run every day 11.15 a.m
Every time when the script is executed i get a mail but when i run it using crontab it doesn't send any mail.
However... (1 Reply)
Hi all,
I'm having a problem with a crontab entry execution for a non root user.
AIX version 5.3
user@host ~ $ oslevel -r
5300-10
cron status
user@host ~ $ ps -ef | grep cron
root 377044 1 0 Oct 27 - 0:22 /usr/sbin/cron
cron entry for user
user@host ~ $... (3 Replies)
Hi,
I have a cronjob but it is not getting executed.Is there any ways to check whether crontab is working.I have put crontab -l and checked.It got listed.But it is not working.
My Crontab is,
* * * * * /ldesk/home/abc/source/compare.sh >/dev/null 2>&1 (1 Reply)
hi,
i have schduled a job through crontab, but it is not getting executed.
bash-3.2$ crontab -l
# Monthly Download (mm hh DD MM format)
35 05 01 04 * /home/ftpsrp/srpftp1/download/ofrdb/scripts/load_ofrdb.sh crr.sh
here is the permission of the .sh files
-rwxr--r-- 1 ftpsrp srp ... (7 Replies)
My colleague who was a sysadmin , has created a cron job script which collects logs and process them.
The script works perfectly as per the defined time set by him.
it works when we keep the timing as 55 05 * * * , whereas if we try to prepone the cron task is not getting executed.
Where... (10 Replies)
Hello,
I have a bash script that finds files older than 31 days and deletes them. I have this file loading into crontab to run everyday. It ran fine the first time i loaded it in, but now when I try to run it manually (bash file.sh) I get errors.
Here is the script
TIME=" -maxdepth 1... (6 Replies)
Discussion started by: jrymer
6 Replies
LEARN ABOUT BSD
sticky
STICKY(8) System Manager's Manual STICKY(8)NAME
sticky - persistent text and append-only directories
DESCRIPTION
The sticky bit (file mode bit 01000, see chmod(2)) is used to indicate special treatment for certain executable files and directories.
STICKY TEXT EXECUTABLE FILES
While the `sticky bit' is set on a sharable executable file, the text of that file will not be removed from the system swap area. Thus the
file does not have to be fetched from the file system upon each execution. Shareable text segments are normally placed in a least-fre-
quently-used cache after use, and thus the `sticky bit' has little effect on commonly-used text images.
Sharable executable files are made by the -n and -z options of ld(1).
Only the super-user can set the sticky bit on a sharable executable file.
STICKY DIRECTORIES
A directory whose `sticky bit' is set becomes an append-only directory, or, more accurately, a directory in which the deletion of files is
restricted. A file in a sticky directory may only be removed or renamed by a user if the user has write permission for the directory and
the user is the owner of the file, the owner of the directory, or the super-user. This feature is usefully applied to directories such as
/tmp which must be publicly writable but should deny users the license to arbitrarily delete or rename each others' files.
Any user may create a sticky directory. See chmod(1) for details about modifying file modes.
BUGS
Since the text areas of sticky text executables are stashed in the swap area, abuse of the feature can cause a system to run out of swap.
Neither open(2) nor mkdir(2) will create a file with the sticky bit set.
4th Berkeley Distribution May 26, 1986 STICKY(8)