Hi,

The module seems to be working great, only issue I came across is that when CRON job is running and suppose to remove the files - it doesn't. The module reports the following error :

rmdir(-------/cache/------/0/directory) [function.rmdir]: Directory not empty in ------/modules/boost/boost.helpers.inc on line 35.

Seems like the recursive function for removing the old files and directories isn't functioning okay. Any ideas?

Comments

Arto’s picture

Arto commented
Assigned: Unassigned » Arto

Thanks for reporting! This watchdog error message is more annoying than critical - it's just an artefact of how the recursive expiry mechanism works at present. Any expired files should be removed fine (please explicitly indicate if they don't, as that would bad, obviously), while cache directories that still contain any non-expired files can't (and of course, shouldn't) be removed and thus result in this message being output.

I'll get rid of this spurious error message asap.

PS. There was an important bugfix to Boost yesterday that fixes symlink creation (for Drupal URL aliases) on Linux platforms. I recommend you update your module from CVS if you're using it on a Linux system.

Arto’s picture

Arto commented
Status: Active » Fixed

Fixed in CVS commit #46331.

fiLi’s picture

fiLi commented

Seems to be working okay.

Thanks a lot for the ultra quick response and fix.

Arto’s picture

Arto commented
Version: » 4.7.x-1.x-dev
Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)
imoreno’s picture

imoreno commented
Version: 4.7.x-1.x-dev » 7.x-1.x-dev
Assigned: Arto » Unassigned
Status: Closed (fixed) » Active

Not sure if this is the right place - but the same issue is now happening with 7.x-1.x-dev ,

Warning: rmdir(cache/normal/www.mysite.com//sites/default/files) [function.rmdir]: Directory not empty public_html/sites/all/modules/boost/boost.module

boost is working great - this looks just like a message on cron run that can be ignored.
should it be fixed?

bgm’s picture

bgm commented
Version: 7.x-1.x-dev » 4.7.x-1.x-dev
Status: Active » Closed (fixed)

@ imoreno : please open a new bug report. It's a similar issue, but not linked to the Drupal 4.7 issue. (and to avoid bugging the people who participated in the bug report from 5-6 years ago)