|
|
Sponsored Content
Top Forums
UNIX for Advanced & Expert Users
Script only runs first time through crontab
Post 302984406 by hasn318 on Tuesday 25th of October 2016 03:01:11 PM
10-25-2016
|
|
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have a crontab as below:
PATH=/usr/local/sbin:/bin/:..... etc etc
0 8 * * * /home/user/jobs/poll.sh 2>/dev/null 1>/dev/null
Now the script poll.sh is called at correct time and executes.
This is how poll.sh looks like
#!/bin/bash... (2 Replies)
Discussion started by: chakrapani
2 Replies
2. Shell Programming and Scripting
Hi all
I have this inside a shell script (bash):
cd DIRECTORY
find . -maxdepth 1 | sed 's#./##' | /usr/bin/xargs -I '{}' chown -Rv '{}' /DIRECTORY/'{}'
All the directories in this location are named after usernames, so it simply sets the owner to that of the username of the folder.
It... (5 Replies)
Discussion started by: fakesy
5 Replies
3. Shell Programming and Scripting
Hello all,
I'm new here and have a question if you don't mind helping me. I have a script that will work if I kick if off manually but not from Cron. My cron entry is this:
05,20,35,50 * * * * /scripts/status.sh > /dev/null 2>&1
The first script (works fine) is this:
#!/bin/sh
#
#... (14 Replies)
Discussion started by: hs3082
14 Replies
4. Shell Programming and Scripting
Hello Guys,
I have scratched my head alot on this but couldn't find clue what's wrong. Can you please help me with this? My problem is as following.
1) When I manually execute following script it runs successfully with below output.
bash-3.00# more smssend
#!/bin/bash
echo -e "<Request... (16 Replies)
Discussion started by: umarsatti
16 Replies
5. Shell Programming and Scripting
Hello Team,
As a part of my job we have made a script to automate a service to restart frequently.
Script having two functions when executing it's should find the existing service and kill it, then start the same service . Verified the script it's working fine when executing... (18 Replies)
Discussion started by: gowthamakanthan
18 Replies
6. Shell Programming and Scripting
Hello All,
I have created a shell script, When i run it manually as ./<script_name> it takes 5 hours to run, but when i am scheduling it in crontab, it is taking 20 hours to run.
Please help me and advice, what can be done to reduce the time in crontab.
Thank you (6 Replies)
Discussion started by: anand2308
6 Replies
7. Shell Programming and Scripting
Hello Gurus,
I have written small script which will start the given service if its stop .Its running fine when manually executed but its unable to run from crontab.
#!/bin/bash
SERVICENAME=rsyslog
service $SERVICENAME status > /dev/null
SYSLOGSTATUS=`echo $?`
COUNT=0
THRESHOLD=3
if ... (4 Replies)
Discussion started by: kapil514
4 Replies
8. UNIX for Dummies Questions & Answers
Hi Guys,
I am executing the script called Delet.sh manually it is successfully completing the task but it is failing to run vi cron tab, I tried to pass PATH & .profile before execution but no luck, Any suggestions?
Script below
#!/usr/bin/ksh
#set -x
# Purpose : Delete folders file from... (9 Replies)
Discussion started by: Anilsa77
9 Replies
9. Shell Programming and Scripting
I have a script (/home/admin/run_bkup.sh) that I can run manually to kick off an executable job. I want to run it in crontab, but it doesn't work.
Here's the script:
shell=/bin/bash
today=$(date +"%m-%d-%y")
/opt/CPsuite-R77/fw1/bin/upgrade_tools/upgrade_export mgt-svr-bkup-$today << EOF
y... (18 Replies)
Discussion started by: df08388
18 Replies
10. Shell Programming and Scripting
Hi,
Attached is a generated script of the database files if/when we want to run dbv = dbverify.
The script runs fine by itself but it does take awhile to finish. In a worse case scenario, it can take up to 7 hours to finish as the dbv runs serially.
I need help and guidance to somehow... (5 Replies)
Discussion started by: newbie_01
5 Replies
LEARN ABOUT OPENDARWIN
su
SU(1) BSD General Commands Manual SU(1) NAME
su -- substitute user identity SYNOPSIS
su [-flm] [login] [-c shell arguments] DESCRIPTION
su requests the password for login and switches to that user and group ID after obtaining proper authentication. A shell is then executed, and any additional shell arguments after the login name are passed to the shell. If su is executed by root, no password is requested and a shell with the appropriate user ID is executed. The options are as follows: -c Invoke the following command in a subshell as the specified user. -f If the invoked shell is csh(1), this option prevents it from reading the ``.cshrc'' file. -l Simulate a full login. The environment is discarded except for HOME, SHELL, PATH, TERM, and USER. HOME and SHELL are modified as above. USER is set to the target login. PATH is set to ``/bin:/usr/bin''. TERM is imported from your current environment. The invoked shell is the target login's, and su will change directory to the target login's home directory. This option is identical to just passing "-", as in "su -". -m Leave the environment unmodified. The invoked shell is your login shell, and no directory changes are made. As a security precau- tion, if the target user's shell is a non-standard shell (as defined by getusershell(3)) and the caller's real uid is non-zero, su will fail. The -l and -m options are mutually exclusive; the last one specified overrides any previous ones. Only users in group ``wheel'' (normally gid 0) or group ``admin'' (normally gid 20) can su to ``root''. By default (unless the prompt is reset by a startup file) the super-user prompt is set to ``#'' to remind one of its awesome power. SEE ALSO
csh(1), login(1), sh(1), skey(1), kinit(1), kerberos(1), passwd(5), group(5), environ(7) ENVIRONMENT
Environment variables used by su : HOME Default home directory of real user ID unless modified as specified above. PATH Default search path of real user ID unless modified as specified above. TERM Provides terminal type which may be retained for the substituted user ID. USER The user ID is always the effective ID (the target user ID) after an su unless the user ID is 0 (root). HISTORY
A su command appeared in Version 7 AT&T UNIX. BSD
April 18, 1994 BSD