10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi Team,
I have written the shell script which returns the result of the disk space filesystems which has crossed the threshold limit in HTML Format. Below mentioned is the script which worked perfectly on QA system.
df -h | awk -v host=`hostname` '
BEGIN {
print "<table border="4"... (13 Replies)
Discussion started by: Harihsun
13 Replies
2. Shell Programming and Scripting
Hello, Newbie here,
I have a perfectly well working web service call I can issue from chrome (PC Windows 10) and get the results I want (a dimmer being turned on in Fibaro Home Center 2 at level 40)
I am not allowed to post urls but the below works with http and :// and... (3 Replies)
Discussion started by: abigbear
3 Replies
3. Shell Programming and Scripting
We have lftp command inside shell file. which is intern calling .cfg file for transferring the file from one server to other.
Below command to not working.
lftp -e "set net:max-retries 1; set net:reconnect-interval-base 1; put -E -O /destinationdir/inbox/ /sourcedir/test.txt; bye" -u... (4 Replies)
Discussion started by: johnsnow
4 Replies
4. Solaris
iam withdrawing this thread , It was my mistake I didn't read the code properly (0 Replies)
Discussion started by: boncuk
0 Replies
5. Shell Programming and Scripting
I am trying to automate a script where I need to use pbrun /bin/su but for some reason it is not passing thru the pbrun as my code below.
. ~/.bash_profile
pbrun /bin/su - content
c h 1
hpsvn up file path
I am executing this from an external .sh file that is pointing to this scripts file... (14 Replies)
Discussion started by: jorgejac
14 Replies
6. Red Hat
Hi Team
we have created a DNS server at RHEL6.2 environment in 10.20.203.x/24 network.
Everything is going well on linux client as nslookup, ping by host etc in entire subnet. We are getting problem in windows client as nslookup working as well but not ping. all the firewall is disabled and... (5 Replies)
Discussion started by: boby.kumar
5 Replies
7. Shell Programming and Scripting
Help. My script is working fine when executed manually but the cron seems not to catch up the command when registered.
The script is as follow:
#!/bin/sh
for file in file_1.txt file_2.txt file_3.txt
do
awk '{ print "0" }' $file > tmp.tmp
mv tmp.tmp $file
done
And the cron... (2 Replies)
Discussion started by: jasperux
2 Replies
8. Linux
Dear all,
I am totally despaired and puzzled.
Using Filezilla under Windows under the same network as our Linux servers is working. Using FTP command-line client under any of our Linux debian servers is not working ! I tried with different FTP servers -> same problem !
All commands are... (12 Replies)
Discussion started by: magix_ch
12 Replies
9. Shell Programming and Scripting
Hi,
I need to zip/compress a data file and send to a vendor. The vendor does have only unzip utility and can accept only .ZIP files. I do not have zip utility in my server.
How do I zip/compress the file so that it can be deflated using unzip command ? I tried gzip & compress commands, but... (1 Reply)
Discussion started by: Sabari Nath S
1 Replies
10. Shell Programming and Scripting
#!/usr/bin/bash
name="$@"
myname=malay
#echo $myname
select firstname in $name;
do
if ;then
echo $firstname
else
break
fi
done
invoking with:-
./script.sh one two three four five six seven eight nine malay (6 Replies)
Discussion started by: mobydick
6 Replies
CRON(8) System Manager's Manual CRON(8)
NAME
cron - daemon to execute scheduled commands (Vixie Cron)
SYNOPSIS
cron [-f] [-l] [-L loglevel]
DESCRIPTION
cron is started automatically from /etc/init.d on entering multi-user runlevels.
OPTIONS
-f Stay in foreground mode, don't daemonize.
-l Enable LSB compliant names for /etc/cron.d files
-L loglevel
Sets the loglevel for cron. The standard logging level (1) will log the start of all the cron jobs. A higher loglevel (2) will
cause cron to log also the end of all cronjobs, which can be useful to audit the behaviour of tasks run by cron. Logging will be
disabled if the loglevel is set to zero (0).
NOTES
cron searches its spool area (/var/spool/cron/crontabs) for crontab files (which are named after accounts in /etc/passwd); crontabs found
are loaded into memory. Note that crontabs in this directory should not be accessed directly - the crontab command should be used to
access and update them.
cron also reads /etc/crontab, which is in a slightly different format (see crontab(5)). Additionally, cron reads the files in /etc/cron.d:
it treats the files in /etc/cron.d as in the same way as the /etc/crontab file (they follow the special format of that file, i.e. they
include the user field). However, they are independent of /etc/crontab: they do not, for example, inherit environment variable settings
from it. The intended purpose of this feature is to allow packages that require finer control of their scheduling than the
/etc/cron.{daily,weekly,monthly} directories to add a crontab file to /etc/cron.d. Such files should be named after the package that sup-
plies them. Files must conform to the same naming convention as used by run-parts(8): they must consist solely of upper- and lower-case
letters, digits, underscores, and hyphens. If the -l option is specified, then they must conform to the LSB namespace specification,
exactly as in the --lsbsysinit option in run-parts.
Like /etc/crontab, the files in the /etc/cron.d directory are monitored for changes. In general, the admin should not use /etc/cron.d/, but
use the standard system crontab /etc/crontab.
In contrast to the spool area, files in /etc/cron.d may be symlinks, provided that both the symlink and the file it points to are owned by
root.
cron then wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current minute.
When executing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable in the
crontab, if such exists). The children copies of cron running these processes have their name coerced to uppercase, as will be seen in the
syslog and ps output.
Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab) has changed, and if it has,
cron will then examine the modtime on all crontabs and reload those which have changed. Thus cron need not be restarted whenever a crontab
file is modified. Note that the crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
Special considerations exist when the clock is changed by less than 3 hours, for example at the beginning and end of daylight savings time.
If the time has moved forwards, those jobs which would have run in the time that was skipped will be run soon after the change. Con-
versely, if the time has moved backwards by less than 3 hours, those jobs that fall into the repeated time will not be re-run.
Only jobs that run at a particular time (not specified as @hourly, nor with '*' in the hour or minute specifier) are affected. Jobs which
are specified with wildcards are run based on the new time immediately.
Clock changes of more than 3 hours are considered to be corrections to the clock, and the new time is used immediately.
cron logs its action to the syslog facility 'cron', and logging may be controlled using the standard syslogd(8) facility.
ENVIRONMENT
If configured in /etc/default/cron in Debian systems, the cron daemon localisation settings environment can be managed through the use of
/etc/environment or through the use of /etc/default/locale with values from the latter overriding values from the former. These files are
read and they will be used to setup the LANG, LC_ALL, and LC_CTYPE environment variables. These variables are then used to set the charset
of mails, which defaults to 'C'.
This does NOT affect the environment of tasks running under cron. For more information on how to modify the environment of tasks, consult
crontab(5).
The daemon will use, if present, the definition from /etc/timezone for the timezone.
The environment can be redefined in user's crontab definitions but cron will only handle tasks in a single timezone.
SEE ALSO
crontab(1), crontab(5)
AUTHOR
Paul Vixie <paul@vix.com>
4th Berkeley Distribution 19 April 2010 CRON(8)