Sponsored Content
Top Forums Shell Programming and Scripting General Q: how to run/schedule a php script from cron jobs maybe via bash from shell? Post 302317195 by lowmaster on Monday 18th of May 2009 09:32:08 AM
Old 05-18-2009
Ok, I have extended the script so now it looks like this.

As told above, logging in, and loading the correct dialog screen works well. Now I have to fill the form and send its content to the server via POST Variables.

I could research, that something like this should work, but I seem to have errors in it, as I have only the same result as above. I still get the formular loaded in the html file, but expect to see something else. What I dont understand is how does the script press the Submit "go" button? Testwise I fill the variable:searchterm=anysearchword

<?php
$username="test";
$password="test";
$cookie="cookies.txt";
$url="http://192.168.0.234/";
$postdata = "log=". $username ."&pwd=". $password ."&subm-cia=Log%20In&redir_to=". $url ."cia/edit.php?page=CIA.php";
$ch = curl_init();
curl_setopt ($ch, CURLOPT_URL, $url . "login-cia.php");
curl_setopt ($ch, CURLOPT_USERAGENT, "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)");
curl_setopt ($ch, CURLOPT_SSL_VERIFYPEER, FALSE);
curl_setopt ($ch, CURLOPT_TIMEOUT, 60);
curl_setopt ($ch, CURLOPT_FOLLOWLOCATION, 1);
curl_setopt ($ch, CURLOPT_RETURNTRANSFER, 0);
curl_setopt ($ch, CURLOPT_COOKIEJAR, $cookie);
curl_setopt ($ch, CURLOPT_REFERER, $url . "login-cia.php");
curl_setopt ($ch, CURLOPT_POSTFIELDS, $postdata);
curl_setopt ($ch, CURLOPT_POST, 1);
$result = curl_exec ($ch);


function curlStart($domain, $var = false){
$fp = curl_init($domain);
curl_setopt($fp,CURLOPT_TIMEOUT,60);
curl_setopt($fp,CURLOPT_FAILONERROR,0);
curl_setopt($fp,CURLOPT_RETURNTRANSFER,1);

if($var != false) {
curl_setopt($fp,CURLOPT_POST,1);
curl_setopt ($fp, CURLOPT_POSTFIELDS, $var);
}

curl_exec($fp);

if(curl_errno($fp) != 0) {
$send = FALSE;
} else {
$send = TRUE;
}

curl_close($fp);

return $send;

}

$formURL = 'http://192.168.0.234/cia/edit.php?page=CIA.php';
$var = 'searchterm=anysearchword';

for($x=0;$x<1;$x++) {
$send = curlStart($formURL,$var);
}

exit;
?>
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

schedule many jobs using cron

HI, I need to schedule a no.of jobs using the cron facility. I currently do two kinds of scheduling,one based on the database load(after the database is loaded the program will start) and the other is based on time.....(say 10.00a.m daily) the problem is.......... When the database is loaded... (1 Reply)
Discussion started by: sireesha15
1 Replies

2. Linux

cron jobs not run

hi, I am newbie, I had set cron jobs to update something on one time very day, I had tested the script, it run fine, but the cron jobs seem never run. some help? Thanks. (4 Replies)
Discussion started by: robertsnoog
4 Replies

3. UNIX for Dummies Questions & Answers

Please help me with the run-away cron jobs

I started a cron job on a cluster super computer. I am just a usual user over there and has no root power. The cron job was set by using "crontab -e". It excecutes a perl command every 20 minutes. I could use crontab -l or crontab -r to list or remove the cron job. However, I just found that I... (2 Replies)
Discussion started by: dedema
2 Replies

4. UNIX for Dummies Questions & Answers

shell script run by user or cron job ?

My shell script runs fine both as a cron job and when i issue it. However, I wish to differentiate when it runs as a cron-job so the "echo" statements are not issued (they get mailed to me, which i don't want). I tried checking $USER but since the cron was created in my user that does not... (5 Replies)
Discussion started by: sentinel
5 Replies

5. Shell Programming and Scripting

Shell script to schedule jobs

Dear all, I have to create a shell script which will run the job during weekday/weekend in following manner: - There are 3 jobs JB_1 JB_2 JB_3 These jobs changes its flag to "COMPLETED" in below 2 ways 1. These 3 jobs which runs after the completion of previous one i.e JB_1 runs and... (5 Replies)
Discussion started by: prajaktaraut
5 Replies

6. Shell Programming and Scripting

how do I run bash script using cron job

How do I run bash script using a cron job? I have tried to just write the path of the script, but that didn't work. (1 Reply)
Discussion started by: locoroco
1 Replies

7. Shell Programming and Scripting

Shell Script to Delete Old Cron Jobs

I have a cron entry to deploy a website portal from a staging server to a series of production servers on a weekly basis. On occasion, a random office worker who knows nothing about Linux let alone cron, will be tasked to update news picks on the staging server and then run a manual deployment... (2 Replies)
Discussion started by: AndrewT
2 Replies

8. Shell Programming and Scripting

Schedule and Run By weekly shell script in cronjob

Hi All, How to schedule a shell script(script name- byweeklyreport.sh) it should run by weekly in corn job or is there any script have to write to check week and then run the above script. example-1st run March 06 2013 2nd run March 20 2013 3rd run April 3 2013... (13 Replies)
Discussion started by: krupasindhu18
13 Replies

9. Shell Programming and Scripting

Shell script to run multiple jobs and it's dependent jobs

I have multiple jobs and each job dependent on other job. Each Job generates a log and If job completed successfully log file end's with JOB ENDED SUCCESSFULLY message and if it failed then it will end with JOB ENDED with FAILURE. I need an help how to start. Attaching the JOB dependency... (3 Replies)
Discussion started by: santoshkumarkal
3 Replies

10. UNIX for Beginners Questions & Answers

How to run multiple cron jobs?

I have two scripts which I'm tying to run one after the other- this is what I've tried: 00 14 * * * /path/one.sh && /path/two.sh I've also tried putting each script on a different line: 00 14 * * * /path/one.sh 00 14 * * * /path/two.sh Can this be done? (1 Reply)
Discussion started by: $shell_Learner
1 Replies
WHIPTAIL(1)                                                   General Commands Manual                                                  WHIPTAIL(1)

NAME
whiptail - display dialog boxes from shell scripts SYNOPSIS
whiptail [ --title title ] [ --backtitle backtitle ] [ --clear ] [ --default-item string ] [ --defaultno ] [ --fb ] [ --nocancel ] [ --yes-button text ] [ --no-button text ] [ --ok-button text ] [ --cancel-button text ] [ --noitem [ ] --output-fd fd ] [ --separate-output ] [ --scrolltext ] [ --topleft ] box-options DESCRIPTION
whiptail is a program that will let you present a variety of questions or display messages using dialog boxes from a shell script. Cur- rently, these types of dialog boxes are implemented: yes/no box, menu box, input box, message box, text box, info box, checklist box, radiolist box, gauge box, and password box. OPTIONS
--clear The screen will be cleared to the screen attribute on exit. This doesn't work in an xterm (and descendants) if alternate screen switching is enabled, because in that case slang writes to (and clears) an alternate screen. --defaultno The dialog box will open with the cursor over the No button. --default-item string Set the default item in a menu box. Normally the first item in the box is the default. --fb, --fullbuttons Use full buttons. (By default, whiptail uses compact buttons). --nocancel The dialog box won't have a Cancel button. --yes-button text Set the text of the Yes button. --no-button text Set the text of the No button. --ok-button text Set the text of the Ok button. --cancel-button text Set the text of the Cancel button. --noitem The menu, checklist and radiolist widgets will display tags only, not the item strings. The menu widget still needs some items spec- ified, but checklist and radiolist expect only tag and status. --notags Don't display tags in the menu, checklist and radiolist widgets. --separate-output For checklist widgets, output result one line at a time, with no quoting. This facilitates parsing by another program. --output-fd fd Direct output to the given file descriptor. Most whiptail scripts write to standard error, but error messages may also be written there, depending on your script. --title title Specifies a title string to be displayed at the top of the dialog box. --backtitle backtitle Specifies a backtitle string to be displayed on the backdrop, at the top of the screen. --scrolltext Force the display of a vertical scrollbar. --topleft Put window in top-left corner. -h, --help Print a help message and exit. -v, --version Print version information and exit. Box Options --yesno text height width A yes/no dialog box of size height rows by width columns will be displayed. The string specified by text is displayed inside the dialog box. If this string is too long to be fit in one line, it will be automatically divided into multiple lines at appropriate places. The text string may also contain the sub-string " " or newline characters ` ' to control line breaking explicitly. This dialog box is useful for asking questions that require the user to answer either yes or no. The dialog box has a Yes button and a No button, in which the user can switch between by pressing the TAB key. --msgbox text height width A message box is very similar to a yes/no box. The only difference between a message box and a yes/no box is that a message box has only a single OK button. You can use this dialog box to display any message you like. After reading the message, the user can press the ENTER key so that whiptail will exit and the calling shell script can continue its operation. --infobox text height width An info box is basically a message box. However, in this case, whiptail will exit immediately after displaying the message to the user. The screen is not cleared when whiptail exits, so that the message will remain on the screen until the calling shell script clears it later. This is useful when you want to inform the user that some operations are carrying on that may require some time to finish. --inputbox text height width [init] An input box is useful when you want to ask questions that require the user to input a string as the answer. If init is supplied it is used to initialize the input string. When inputing the string, the BACKSPACE key can be used to correct typing errors. If the input string is longer than the width of the dialog box, the input field will be scrolled. On exit, the input string will be printed on stderr. --passwordbox text height width [init] A password box is similar to an input box, except the text the user enters is not displayed. This is useful when prompting for pass- words or other sensitive information. Be aware that if anything is passed in "init", it will be visible in the system's process ta- ble to casual snoopers. Also, it is very confusing to the user to provide them with a default password they cannot see. For these reasons, using "init" is highly discouraged. --textbox file height width A text box lets you display the contents of a text file in a dialog box. It is like a simple text file viewer. The user can move through the file by using the UP/DOWN, PGUP/PGDN and HOME/END keys available on most keyboards. If the lines are too long to be displayed in the box, the LEFT/RIGHT keys can be used to scroll the text region horizontally. For more convenience, forward and backward searching functions are also provided. --menu text height width menu-height [ tag item ] ... As its name suggests, a menu box is a dialog box that can be used to present a list of choices in the form of a menu for the user to choose. Each menu entry consists of a tag string and an item string. The tag gives the entry a name to distinguish it from the other entries in the menu. The item is a short description of the option that the entry represents. The user can move between the menu entries by pressing the UP/DOWN keys, the first letter of the tag as a hot-key. There are menu-height entries displayed in the menu at one time, but the menu will be scrolled if there are more entries than that. When whiptail exits, the tag of the chosen menu entry will be printed on stderr. --checklist text height width list-height [ tag item status ] ... A checklist box is similar to a menu box in that there are multiple entries presented in the form of a menu. You can select and deselect items using the SPACE key. The initial on/off state of each entry is specified by status. On exit, a list of the tag strings of those entries that are turned on will be printed on stderr. --radiolist text height width list-height [ tag item status ] ... A radiolist box is similar to a menu box. The only difference is that you can indicate which entry is currently selected, by set- ting its status to on. --gauge text height width percent A gauge box displays a meter along the bottom of the box. The meter indicates a percentage. New percentages are read from standard input, one integer per line. The meter is updated to reflect each new percentage. If stdin is XXX, the first following line is a percentage and subsequent lines up to another XXX are used for a new prompt. The gauge exits when EOF is reached on stdin. NOTES
whiptail interprets arguments starting with a dash "-" as being arguments. To avoid this, and start some text in, for example, a menubox item, with a dash, whiptail honours the getopt convention of accepting the special argument "--" which means that all following arguments with dashes are to be treated verbatim and not parsed as options. DIAGNOSTICS
Exit status is 0 if whiptail is exited by pressing the Yes or OK button, and 1 if the No or Cancel button is pressed. Otherwise, if errors occur inside whiptail or whiptail is exited by pressing the ESC key, the exit status is 255. AUTHOR
Based on the man page for dialog(1) by: Savio Lam (lam836@cs.cuhk.hk) - version 0.3 Stuart Herbert (S.Herbert@sheffield.ac.uk) - patch for version 0.4 Modifications for whiptail by: Enrique Zanardi (ezanard@debian.org) Alastair McKinstry (mckinstry@debian.org) Whiptail Version 0.52.5 31 January 2007 WHIPTAIL(1)
All times are GMT -4. The time now is 01:44 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy