Help needed with small VMWare integration issue(s)

All

Loving unRaid.

Following lots of trial and error (and a good deal of fun), I managed to get VMWare running on my 4.5.4 server plus. (thanks to all who've posted guides & tips here).

The various .vm* files and temp directories are located on my cache drive (.custom) and I've happily installed Turnkey LAMP (http://www.turnkeylinux.org/lamp) which gives me a full web dev. sandbox running on top of unRaid and has allowed me consolidate several machines into one. Happy days.

Now, I have two issues that I could do with a bit of advice on.

1. My cache mover runs each evening at 22.00. Since adding the .custom directory to the cache drive, I note that the syslog is now filled with references to each file in that directory. eg.

Sep 20 22:00:01 Tower logger: ./.custom/vmware/usr/lib/vmware/lib/libcurl.so.4/libcurl.so.4

While not a major issue per se, it's filling the log file and making it difficult to read. Any way to stop these 'hidden' files from being processed/logged?

2. I had added a cron job to my system that shuts the server down safely each night at 01.00. (power saving). The script checks to make sure each drive is spun down before doing so and aborts if a drive is spinning (likely in use for some reason).

Now, since enabling vmware server, my cache drive is constantly spun up and the system therefore does not shut down. I suspect this is because vmware server is using/polling that drive. Any thoughts on a solution?

My ideas are;

A. Move VMWARE files to a different (non raid/cache) drive

B. Ignore spun-up status of cache drive and shut down anyway

C. Somehow configure VMWARE to shut itself down half an hour before unraid shutdown is scheduled

I don't want to do A because it would require a recompile of vmware into unraid (shudders)

B sounds fairly dangerous

C I'm not sure how to go about - another cronjob maybe?

Any advice?

Peter

PS Not looking forward to having to recompile vmware into 5.0 stable when it comes out :-(