[EMAIL PROTECTED] writes:
> i've been learning perl for the sole purpose of creating what's
> below. excited by the fact that it's working and it's a start, i
> wanted to get it out tonight for people to look at before i go crash.
:-)
We used to do perl, until we found out that we couldn't decypher
programs we wrote after two weeks.
> 2. i haven't thought a lot yet about how to handle the fact that doing
> this can potentially chew up a ton of disk space. i'm just
> handling it at the moment with a cron job that wipes out all the
> jobs every half hour. so,
> a. don't clobber me by sending 20 jobs in 15 minutes that each
> result in 1 meg postscript files.
> b. don't start a job at 1:29. :-)
>
maybe you can use the tmpwatch program from redhat to handle b. You
can also limit the size of the submitted file. Or you can use quota
and ulimit to limit the resource usage of `remote LilyPond'
--
Han-Wen Nienhuys, [EMAIL PROTECTED] ** GNU LilyPond - The Music Typesetter
http://www.cs.uu.nl/people/hanwen/lilypond/index.html
