1) i have a script which builds up daily tarballs of ucw, currently this runs on my laptop everynight a midnight. i'd be a lot more realiable (i'm not always connected) if it ran directly on the cl.net machine. would there be any problems with running this as a cron job? the overhead would be minimal (copy, tar then bzip about 3 MB of text files).
2) i'd like to, eventually, run an instance of ucw so that people could play with it without having to install it. this would probably be easiest if it ran behind it's own copy of apache with mod_lisp installed. however, this could, potentially, use up a good bit of cpu (ucw isn't exactly optimized yet).
anyway, feel free to simply ignore both of these requests for any reason. they'd make my life easier, but neither is a show stopper.
On May 2, 2004, at 1:27 PM, Marco Baringer wrote:
- i have a script which builds up daily tarballs of ucw, currently this runs on my laptop everynight a midnight. i'd be a lot more realiable (i'm not always connected) if it ran directly on the cl.net machine. would there be any problems with running this as a cron job? the overhead would be minimal (copy, tar then bzip about 3 MB of text files).
Not really a problem but I'm hesitant to say yes incase we all of a sudden have 50 or so cronjobs (one per project) running. That would bog down the server.
What do you guys think?
Rsync is now running on clnet, would that help you in any way?
- i'd like to, eventually, run an instance of ucw so that people could play with it without having to install it. this would probably be easiest if it ran behind it's own copy of apache with mod_lisp installed. however, this could, potentially, use up a good bit of cpu (ucw isn't exactly optimized yet).
I'm pretty happy to do this (we were going to try to use clhp too but the author never replied when I ran into some installation problems). I'll need a detalied step by step guide on how to install it.
Erik.
On Sun, 2 May 2004, Erik Enge wrote:
Not really a problem but I'm hesitant to say yes incase we all of a sudden have 50 or so cronjobs (one per project) running. That would bog down the server.
I agree, but I suspect simple enough solutions exist. How about /project/*/daily.sh, which are run sequentially with appropriate ulimits?
Cheers,
-- Nikodemus
On May 2, 2004, at 5:40 PM, Nikodemus Siivola wrote:
I agree, but I suspect simple enough solutions exist. How about /project/*/daily.sh, which are run sequentially with appropriate ulimits?
That's certainly agreeable. That would give us the ability to keep control. Marco, does that work for you?
Erik.
Erik Enge erik@nittin.net writes:
That's certainly agreeable. That would give us the ability to keep control. Marco, does that work for you?
yes, that'd be fine.