By walterbyrd on

As in cron.php.1, cron.php.2, cron.php.3 and so on. The files are 0 bytes in size, but they are still cluttering up my /root directory. Drupal is the only thing I have running that uses cron.

Running drupal 5.5 on debian etch.

⋅ Categories: Drupal 5.x

Comments

vm’s picture

vm commented

update to the most recent release of 5.x to see if problem can be reproduced on more secure build.

va3pc’s picture

va3pc commented

Drupal 6.10 with all modules up to date.
Running on a SELinux CentOS 4.4 system.
As I run cron every hour, due to simplemail module, I get 24 of these little buggers every day.
Any ideas why this is happening?
Paul

vm’s picture

vm commented

check the simplemail.module issue queue for similar reports and a possible patch.

va3pc’s picture

va3pc commented

Searched the issue queue for cron.php, root, cron and did not come up with any similar reports.
That is unless its the thread about changing users during the mailing process.
I believe that is a D5 based error
Care to give me a hint?
Paul

Saint Aardvark’s picture

Saint Aardvark commented

I had this problem, and I just figured it out. I had:

wget -o /dev/null http://localhost/cron.php

in a script I ran from Linux's crontab (not to be confused with Drupal's crontab). The -o option sends logging output from wget (bytes fetched, elapsed time, etc) but doesn't do anything about the file that's fetched.

Thus, I ended up littering my / directory with cron.php.(whatever), as wget very helpfully avoided clobbering any already-existing instances of cron.php in the root directory.

Changing the invocation to include "-O /dev/null" sent everything to /dev/null, as I'd originally expected.