Sponsored Content
Full Discussion: Cron not working
Operating Systems Linux SuSE Cron not working Post 302968432 by solaris_1977 on Wednesday 9th of March 2016 12:14:13 PM
Old 03-09-2016
Yes, I confirmed that entry is correctly terminated. Still it is not fine.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

cron/crontab not working

Hello All! I'm having problems with cron. First cron is running as a process when i send the top command and I am logged in as root. I type crontab -e to edit/create my cron job. What I'm trying to do is run a perl script on my server (the script does work, i know because I type perl script.pl... (2 Replies)
Discussion started by: ezekiel61
2 Replies

2. UNIX for Dummies Questions & Answers

cron not working

Cron does not seem to work with this crontab. Any ideas? # run-parts # commands to execute every hour 01 * * * * root run-parts /etc/cron.hourly # commands to execute every day 02 4 * * * root run-parts /etc/cron.daily # commands to execute every week 22 4 * * 0 root run-parts... (1 Reply)
Discussion started by: DaleCabell
1 Replies

3. UNIX for Dummies Questions & Answers

Cron not working?

Hello I have a mac os x server machine that I have setup a cron to run a php file using wget and cron doesn't seem to work. I have setup cron on other mac's before and they have all worked. Also I know wget works because I have tested it. Is there anything else I should try? I do crontab -e and... (5 Replies)
Discussion started by: christo16
5 Replies

4. HP-UX

Cron - Not working properly

Hi, I do have three scripts. Whcih inserts records into a table using sqlldr, creating some reprot files etc. The first script will call the second and then the second will call the third. When I run my first script from the shell prompt, all my operation are completed successfully. If I do... (23 Replies)
Discussion started by: risshanth
23 Replies

5. UNIX for Dummies Questions & Answers

Cron not working

I created a file in /u01/oradata directory as cronjb.ksh which contains following script 30 12 * * * /export/home/oracle/u01/oradata/rman.ksh '/export/home/oracle' is my root directory. I then moved cronjb.ksh file to my '/export/home/oracle' directory. i typed crontab cronjb.ksh. However my... (1 Reply)
Discussion started by: manna
1 Replies

6. Shell Programming and Scripting

why isnt cron working?

I am using Ubuntu linux desktop, and I am trying to schedule a sheel script to run every 10minutes. These are the steps I have taken: crontab -e added and saved this line to the file # m h dom mon dow command */1 * * * * /home/enzo/Desktop/dlrecentuse restarted cron: sudo... (5 Replies)
Discussion started by: daydreamer
5 Replies

7. Solaris

cron not working.

I have a script monitor.sh the path is /netmon/bin/monitor.sh when i run this script as sh /netmon/bin/monitor.sh it runs completely fine. but when i include it in crontab , it does not run my cron entry is 0,5,10,15,20,25,30,35,40,45,50,55 * * * *... (11 Replies)
Discussion started by: asalman.qazi
11 Replies

8. Shell Programming and Scripting

Script is not working from cron while working manually

Hello, I am facing a very strange problem when I run my script manuallu ./Fetchcode which is using to connect with MKS integrity from linux end it workks fine but when I run it from cron it doesn't work.Can someone help me 1) How could I check my script when it is running from cron like... (3 Replies)
Discussion started by: anuragpgtgerman
3 Replies

9. Shell Programming and Scripting

cron job now working?

Hi all, I wrote a script as below, #!/bin/ksh . /app/home/etc/sudo.profile >/dev/null java -jar $HOME/abc.jar The jar file abc.jar is located in the same folder as the script. When I'm manually running that script the jar file gets executed. However if I set a cron job, it... (5 Replies)
Discussion started by: isaacniu
5 Replies

10. Shell Programming and Scripting

Script not working in cron but working fine manually

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
dsbl.conf(5)							File Formats Manual						      dsbl.conf(5)

NAME
dsbl.conf - configuration file for all DSBL testers SYNOPSIS
vi /usr/local/etc/dsbl.conf vi ~/.dsblrc DESCRIPTION
dsbl.conf and .dsblrc both control the functioning of the DSBL test programs and DSBL server programs. ~/.dsblrc is read if it exists, otherwise dsbl.conf in $PREFIX/etc is read. (PREFIX is set at compile time and is /usr/local by default. These files are in the format: variable_name="value" variable_name2="value2" Test program variables: sender_user If you were sending tests as test@example.com, you would set sender_user to "test". sender_domain If you were sending tests as test@example.com, you would set sender_domain to "example.com". cookie_host Host to retrieve testing cookies from (cookie.dsbl.org for the DSBL). cookie_user Username to provide to the cookie server to retrieve a cookie. To test anonymously, set this to "". cookie_pass Password to provide to the cookie server to retrieve a cookie. To test anonymously, set this to "". target_user If the listing address is listme@dsbl.org, you would set target_user to "listme". target_domain If the listing address is listme@dsbl.org, you would set target_domain to "dsbl.org". statedir The directory to store the current state (last test date) of IPs. Must be writable by spamtrap(1). checklist The list to check against before testing hosts. If you are an untrusted tester, this should be unconfirmed.dsbl.org, otherwise it should be list.dsbl.org. excluded_ip Each excluded_ip entry is checked against the beginning of an IP before testing. You should list IPs that are local to you and therefor shouldn't be tested. http_port An array of configuration variables to specify which ports HTTP proxies should be tested for on. socks_port An array of configuration variables to specify which ports SOCKS 4 and 5 proxies should be tested for on. message The actual message to send when relay testing. parallel A positive integer representing the number of test processes to run simultaneously. verbosity The amount of information to log to standard output. The options are: 0 No logging 1 Log IP addresses as they are tested 10 Debugging level; log everything Server program variables: mysql_host The hostname to use to connect to the MySQL server. mysql_user The username to use to connect to the MySQL server. mysql_pass The password to use to connect to the MySQL server. mysql_db The name of the DSBL-compliant database on the MySQL server. tempdir The temporary directory in which to store zones while they are being built. This must be on the same filesystem as zonedir. zonedir The directory in which to store the zones once they are built. This must be on the same filesystem as tempdir. unconfirmed_zone The fully qualified domain name of the unconfirmed zone. confirmed_zone The fully qualified domain name of the confirmed (trusted) singlehop zone. multihop_zone The fully qualified domain name of the confirmed (trusted) multihop zone. unconfirmed_nameserver The nameserver of the unconfirmed zone that will be provided in SOA record. confirmed_nameserver The nameserver of the confirmed (trusted) singlehop zone that will be provided in the SOA record. multihop_nameserver The nameserver of the confirmed (trusted) multihop zone that will be provided in the SOA record. zone_contact The contact email address to be provided in the SOA records of both zones. This should have a period (.) instead of an at sign (@). zone_message The TXT message to provide for each IP in the zones. This should end in the dollar sign character ($) which is replaced by the IP in question. listenip The IP address, in dotted quad notation, for the SMTP server to listen on. clientsperip The maximum number of clients per source IP address that will be accepted by the SMTP server. Additional clients from this IP address will be turned away with a temporary error. This is used to prevent attacks from tying up the entire server. idletimeout The time, in seconds, before an idle SMTP session is terminated. This is used to keep server resources available for other connec- tions. AUTHOR
Ian Gulliver <ian@penguinhosting.net> 2002-04-03 dsbl.conf(5)
All times are GMT -4. The time now is 04:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy