Login or Register to Ask a Question and Join Our Community


Shell Programming and Scripting

running Cron job in Plesk

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting running Cron job in Plesk
# 1  
Old 08-28-2009
running Cron job in Plesk
I have a script to delete unwanted cookies from some Curl jobs we are doing

find /tmp -name 'CURLCOOKIE*' -print0 | xargs -0 rm

this works great when I am logged on as root in the shell, now I have to put it into a cron job in Plesk.
When I do that it does not work. I think the directory structure is the problem but am pretty new to linux so I am not sure. I login as admin into plesk.

am I missing something or looking in the wrong directory here? No errors are being thrown. But when I list the /tmp dir in the shell the files are still there. I have the cron job set to run every couple of minutes for now just to see if it works and I have it email me any cron messages. Would set the cron up from the shell but the boss wants to see it in plesk.

Thanks in advance for the help!
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Cron job is not running on schedule

Scheduled job is not running on time.but it is running when executing same command manually. 25 10 * * * /code/bin/ACCOUNT.ksh 1 >/dev/null 2 >&1 Manually executing the same Ksh -x /code/bin/ACCOUNT.ksh 1 >/dev/null 2 >&1 Followed steps Crontab -e Added the job to cron tab. (4 Replies)
Discussion started by: Myguest
4 Replies

2. Shell Programming and Scripting

CRON job still running?

Hi All, I am writing a script that will eventually be executed by a cron job every 15 minutes. I want to make sure that my logic/script doesn't get executed if a previous job is still running. What would be the best way to handle that scenario? I was thinking to make my script create a temporary... (1 Reply)
Discussion started by: rdogadin
1 Replies

3. Solaris

Cron job running even after cron is removed

Hi , I have removed a cron for particular user , but cron job seems to be running even after the cron entry is removed. The purpose of the cron was to sendmail to user ( it uses mailx utility ) I have restarted cron and sendmail service still user is getting mail alerts from the cron job. And... (4 Replies)
Discussion started by: chidori
4 Replies

4. Solaris

Cron job is not running

Hi, I have set up the crontab as follows. root@IDC4VASAPP07 # crontab -l 0-59 * * * * /var/tmp/r.sh 0-59 * * * * date >> /var/tmp/log root@IDC4VASAPP07 # r.sh is as follows. root@IDC4VASAPP07 # cat r.sh #!/bin/bash dt1=$(perl -e 'use POSIX;print strftime... (10 Replies)
Discussion started by: SunilB2011
10 Replies

5. Shell Programming and Scripting

cron job and running program

Dear experts, I have this cronjob * */2 * * * $path/supervisor.sh The supervisor script is checking another script, which initializes the final scripts in multiple directories. Note that the supervisor script runs without the cronjob. In each directory, I have the following script: ... (2 Replies)
Discussion started by: TheTransporter
2 Replies

6. Shell Programming and Scripting

Cron job running problem

Hi Guys, I am trying to run a script through contab. The script can only be executed once user logs in as su - oracle. I have tested the script other then cronjob and it executes successfully, more over the paths used in the script are absolute paths. Crontab entries are as as below.... (3 Replies)
Discussion started by: Asteroid
3 Replies

7. UNIX for Dummies Questions & Answers

Cron job not running

Hi All, I am editing crontab using -e option to add a new job Below is the line 30 * * * * scriptpath This job is not executing every thirty minutes. I have checked, cron daemon is running. What did I miss? Can some one help? I am using cron shell..ksh (7 Replies)
Discussion started by: yabhi_22
7 Replies

8. UNIX for Advanced & Expert Users

cron job is not running

hi, i have the following line in the crontab 15 5 * * 6 /home/adw/BCE_ADW.pl The problem is the cron job is not getting started automatically. But this was working til last week. now it is not working. what could be the problem. Any idea? (3 Replies)
Discussion started by: Suguna
3 Replies

9. Shell Programming and Scripting

Cron job entry not running

Hi, I am facing this problem . My Cronjob entry is not running !!! I am having Sun solaris 9 and cronjob entry is "45 1 * * * /safedir/rdns/opt/RDNS1.1Scripts/drpl_audit_log_script.sh_orig > /dev/null 2>&1" Now when I try to look in the output log files it creates, it is some file with... (1 Reply)
Discussion started by: hkapil
1 Replies

10. HP-UX

Cron Job Not Running

Hi, I have a cron schedule like this 04,16,28,40,52 * * * * /nag/startProcessABatch (unix script) i want to add new lines in this file (like Logging), i just copy this file into a /tmp folder (for backup copy), and i have edited this file (added few lines of code for logging). ... (1 Reply)
Discussion started by: nag_sundaram
1 Replies
Login or Register to Ask a Question

LEARN ABOUT OSF1

jobs

jobs(1) 						      General Commands Manual							   jobs(1)

NAME

       jobs - Displays status of jobs in the current session

SYNOPSIS

       jobs [-l  | -p] job_id...

       [Tru64 UNIX]   jobs [-n] job_id...

									  Note

       The C shell has a built-in version of the jobs command.	If you are using the C shell, and want to guarantee that you are using the command
       described here, you must specify the full path /usr/bin/jobs.  See the csh(1) reference page for a description of the built-in command.

STANDARDS

       Interfaces documented on this reference page conform to industry standards as follows:

       jobs:  XCU5.0

       Refer to the standards(5) reference page for more information about industry standards and associated tags.

OPTIONS

       Provides more information about each job listed. This information includes the job number, current job, process group  ID,  state  and  the
       command	that  formed  the  job.  Displays only the process IDs for the process group leaders of the selected jobs.  [Tru64 UNIX]  Displays
       jobs that have stopped or exited since last notified.

       By default, the jobs utility displays the status of all stopped jobs, running background jobs and all jobs whose status has changed and has
       not been reported by the shell.

OPERANDS

       Specifies  the  jobs  for  which the status is to be displayed.	If no job_id operand is given, the status information for all jobs is dis-
       played.	The format of job_id is described in the Jobs section of the ksh(1) reference page.

DESCRIPTION

       The jobs utility displays the status of jobs that were started in the current shell environment.

       When jobs reports the termination status of a job, the shell removes its process ID from the list of those "known in the current shell exe-
       cution environment".  See the Jobs section of the ksh(1) reference page.

RESTRICTIONS

       The  jobs  utility  does not work as expected when it is operating in its own utility execution environment because that environment has no
       applicable jobs to manipulate.

EXIT STATUS

       The following exit values are returned: Successful completion.  An error occurred.

ENVIRONMENT VARIABLES

       The following environment variables affect the execution of jobs: Provides a default value for the internationalization variables that  are
       unset or null. If LANG is unset or null, the corresponding value from the default locale is used.  If any of the internationalization vari-
       ables contain an invalid setting, the utility behaves as if none of the variables had been defined.  If set to a  non-empty  string  value,
       overrides  the  values of all the other internationalization variables.	Determines the locale for the interpretation of sequences of bytes
       of text data as characters (for example, single-byte as opposed to multibyte characters in  arguments).	 Determines  the  locale  used	to
       affect  the  format  and  contents  of  diagnostic  messages written to standard error and informative messages written to standard output.
       Determines the location of message catalogues for the processing of LC_MESSAGES.

SEE ALSO

       Commands:  bg(1), csh(1), fg(1), kill(1), ksh(1), sh(1p), wait(1)

       Standards:  standards(5)

																	   jobs(1)