Jump to content
The Uniform Server Community

10basetom

Member
  • Content Count

    7
  • Joined

  • Last visited

Everything posted by 10basetom

  1. I know at least Drupal (and possibly other CMS's) can make use of this to improve the file upload experience. It would be nice to have it bundled with the next release (WampServer 2 comes with it). More info here: http://freestylesystems.co.uk/blog/install...field-30-module Here's the Windows binary: http://downloads.php.net/pierre/php_upload...n32-VC6-x86.zip Cheers, Tom
  2. Yup, I just installed Drupal 7 a minute ago and can confirm that nothing broke after ALTERing all the tables to ENGINE=MyISAM.
  3. Does this mean Drupal 7 *requires* InnoDB? I can see this being a problem for many people because most cheap hosts only support MyISAM.
  4. Updated http://wiki.uniformserver.com/index.php/In...pal_on_4.0-Mona Thanks again for your quick help -- my Drupal cron is running smoothly now. Tom
  5. Hi Ric, Your solution works like a charm -- very clever. Upon further inspection I was wrong: there WAS a cmd.exe process running that was reponsible for the infinite loop, so if you kill both cmd.exe and unidelay.exe then unidelay.exe is gone for good. However, I sometimes run several cmd.exe windows and don't want to accidently kill one of them, so your solution is safer . Now did you want to update the cron installation instructions in the wiki? If not, I can do it on your behalf. Tom P.S. I noticed that the current instructions to run run_cron.bat just below :END was causing unidelay.exe to run every time, even when Server_Start.bat errors out (e.g., servers already running), so I'm going to move run_cron.bat just below :NOTFOUND, right before the virtual drive logic: :NOTFOUND echo. echo Starting Drupal cron ............... echo. start udrive\home\admin\program\uniserv.exe run_cron.bat Tom
  6. Hi Ric, Good one . I'm running unidelay.exe from the run_cron.bat as given by the instructions here: http://wiki.uniformserver.com/index.php/In...n_4.0-Mona#Cron Here is my run_cron.bat file: :next udrive\home\admin\program\unidelay.exe 3600 udrive\usr\local\php\php.exe -n udrive\www\drupal\run_cron.php goto :next exit I'm not running unidelay.exe from anywhere else. I noticed that after I stop Uniserver with Stop.bat, the unidelay.exe process is still kicking it, so I went to manually kill it, but it rises from the dead again after about a minute (even though I set my delay to 3600 seconds). In fact, I only noticed this after I added instructions to "pv.exe -k -f unidelay.exe" in Stop.bat. I'm pulling my hair trying to determine what the heck is restarting it because I'm looking at my process list and there's no process related to Uniserver that's running after you run Stop.bat (cmd.exe is also not running). Yeah, unidelay is gone for good after a reboot. Are you able to reproduce this? Try recreating the batch from above and runnining it. I'm using the latest Uniserver: 4.3. Tom *pulling his hair out*
  7. I noticed that about a minute after I kill the unidelay.exe process, it restarts itself. Does anyone know what's restarting it, and how I can permanently kill unidelay.exe? Thanks, Tom
×
×
  • Create New...