On 8/3/05, ryan byrd <[EMAIL PROTECTED]> wrote: > > I think you've seen plenty of suggestions, but at and batch are > > siblings of cron for doing this sort of thing, just to give you some > > more reading to do :-) > > Yeah, I tried using at and batch, but for some reason, they ignored the > #!/usr/local/bin/php at the top of test.php and instead tried to interpret > the php program through /bin/bash and so would consequently throw errors. > > strange > > mrb. >
I'm curious when/why you should/would _not_ use screen... If it was me I'd love screen - I could reattach it later to keep tabs on it - and detach it to let it continue running after I had logged out... ... seems like it's the perfect solution (to say nothing of it's other wonderful abilities). -Rich -------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
