use of /tmp impacts multiple runs

[(chongo) Landon Curt Noll]

As on observation on the use of /tmp by insite:
It turns out that one cannot run multiple insite's at the same time.
This is because each run steps on the other's temp files.

Consider a hosting site that wants to make an insite
tool available to each virtual site.  That could not be
done with the current temp file method.

Consider the case where someone wants to run insite
via cron on a daily basis in addition to running it by
hand on an as needed basis.  If the cron job starts up
while the by-hand run is in progress (or the other way
around) the dual runs step on each other.

The comment dated 05/23/00 12:23 in bug #106290 suggests
one method whereby a one insite run can avoid stepping on
another.  I'm sure other methods exist as well.  I'd suggest that
some consideration of multiple runs be given.

chongo <> /\oo/\

[Jason Priebe]

I agree, this would be a good goal.  I think that I'd like the user to be able to specify a TMP directory (since not all computers have a "/tmp" directory).  Doing all temp work in a subdirectory of the TMP directory would be a good idea to isolate one insite copy from another.  Of course, to be able to run multiple copies of the program on various virtual sites, you'd have to be able to specify a number of different parameters that are hard-coded in the InSiteConfig.pm file right now.  It would probably be best to have a command-line option to allow the user to specify a config file.  Maybe it's time to consider changing the config file to make it a "real" config file, and not perl code...

[Scott Boss]

I currently host 14 (or is it 15) websites for myself and friends on my machine.  By end of summer, I will have at least 20.  Most are very very small but each site is independant of each other.  Each has their own directory structure and webmaster.  I would love to be able to roll this out for them saying that every _____day the script will run and update the information for your site.  If you would like it to run before then click here (which would run it then for the webmaster).  I would like their information to be available to them and only them (I can lock down the webpage via apache) but I need to be able to run this program with independant config files.  I know that alot of people are running mulitple sites on the same box.

Thanks,
Scott

PS:  If you need a site that can test the multiple config setup, please let me know and we can test it out on my machine.