Web Xynga

DNS Services DNS Services Free Web and Internet Directory Free Web and Internet Directory Debt Consolidation Mobile Phone Movie stars Online Loans Mortgage Advertise here Affiliates Reviews Help Youth Defeating Stigma structured settlement news

Configuration of Cron Jobs For Automatic Search Engine Submissions

Next articles: Cloaking and Security Tips #1 - In this series of articles we will feature discussions relating to security issues. Obviously, the term "security" may cover a lot of areas - here we will focus primarily on cloaking... Infoseek-GO Spider Codes Debunked - Many Infoseek spiders originate from hosts that seem to bear a cryptic string of characters in their domain names, e.g. cca26101.infoseek.com... The Google Trap: A Warning - If you happen to use Google's proprietary meta tag... How to Generate Fillertext Content - Phantom pages are web pages offering highly optimized content intended for search engine spiders only. Shadow Domains are dedicated web properties focused on offering optimized content to search engines while... Building Doorway Domains for Optimized Search Engine Positioning - Doorway pages have been around for a long time and most people trying for search engine optimization are more or less familiar with them. To recapitulate: a classical...

by Dirk Brockhausen

Cron is a mechanism for planning and scheduling batch jobs. Implemented on Unix systems, you can use it to schedule automatic submission of URLs to search engines. This takes the hassle out of regular and/or recurring submissions.

The daemon "crond" is started automatically on system boot up. It runs one check per minute to see if there are any jobs to execute.

The list of jobs to execute is created by the program "crontab".

The following commands work from the assumption that you are either logged in by Telnet or locally on your Unix system.

Entering the command "crontab -l" will display a list of current entries. By default, only entries owned by the logged in User will be displayed.

Existing lists can be removed/deleted with command "crontab -r".

To create a new list, it is recommended to read the entries from a file using command "crontab filename".

The following examples will show you the format of this file. The file itself is created with an ASCII text editor.

Example:

0 12 * * * /usr/yourdomain/cgi-bin/subfrog.cgi cron_parm1.txt

This entry consists of six parameters. The first five parameters define the time schedule, whereas the sixth parameter contains the command for executing the job. In our example above, this command consists of:

- the full path and file name of the script - an argument

This latter argument defines the batch configuration for your submission program, e.g. fantomas subFrog PRO(TM).

In fantomas subFrog(TM), this command can be transferred by "cut and pasted" from the list of "Command line strings" displayed in the lower section of the "BATCH MODE CONFIGURATION EDITOR" of the GUI.

Parameters defining the time schedule are:

minute(0-59) hour(0-23) day of month(1-31) month(1-12) day of week(0-6) 0 = Sun

Hence, the above sample entries: 0 12 * * * can be translated as:

If Minute = 0 and Hour = 12, the script will be executed.

Because the last three scheduling parms are defined by wildcard character "*", the job will be executed every day.

Scheduling Week Days If you wish to run the script on Mondays only, the following entry will do the trick:

0 12 * * 1 /usr/yourdomain/cgi-bin/subfrog.cgi cron_parm1.txt

Scheduling Turn of Month You can schedule the turn of the month in this manner:

0 0 1 * * /usr/yourdomain/cgi-bin/subfrog.cgi cron_parm1.txt

Configurations for Multiple Domains If you are maintaining multiple domains, you can create a separate job for each domain.

E.g. you may create a file named "crontabfilename.txt" and enter the following command lines:

0 12 * * * /usr/yourdomain/cgi-bin/subfrog.cgi cron_parm1.txt 0 14 * * * /usr/yourdomain/cgi-bin/subfrog.cgi cron_parm1.txt 0 16 * * * /usr/yourdomain/cgi-bin/subfrog.cgi cron_parm1.txt

The respective argument "domain1.cron.txt" defines the file containing the pertinent domain's batch configuration.

Next, the command "crontab crontabfilename.txt" will transmit this file to crontab.

Important = If you have crontab configured for prior jobs already, you must include them in the new file "crontabfilename.txt" (example), as the command "crontab crontabfilename.txt" will override all previous cron jobs owned by the specific user calling crontab.

For further explanations under Unix, you can select from the following commands:

man crontab man 5 crontab man cron

Find out more about fantomas subFrog PRO(TM) and its features here: < http://fantomaster.com/fasubfrog0.html >

Dirk Brockhausen is the co-founder and principal of fantomaster.com Ltd. (UK) and fantomaster.com GmbH (Belgium), a company specializing in webmasters software development, industrial-strength cloaking and search engine positioning services. He holds a doctorate in physics and has worked as an SAP consultant and software developer since 1994. He is also Technical Editor of fantomNews, a free newsletter focusing on search engine optimization, available at: < http://fantomaster.com/fantomnews-sub.html > You can contact him at mailto:fntecheditor@fantomaster.com

(c) copyright 2001 by fantomaster.com All rights reserved. Downloaded at: < http://fantomaster.com/ >

Link to this article, just copy and paste following code: <a href=http://www.xynga.com/article1256.html>Configuration of Cron Jobs For Automatic Search Engine Submissions</a>

Article viewed 948 time(s). Read more:

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 |