I understand this is a shortcoming of busybox. But it makes AstLinux unattractive for anybody who is scheduling outbound calls. You'd be surprised at how some people feel about that last five minutes of sleep. Reminder calls can't be late.
Can the Touch command really be so large that it can't be included in AstLinux?
On 3/14/06, Kristian Kielhofner <
[EMAIL PROTECTED]> wrote:
Tom Lynn wrote:
> Does the Touch command in BusyBox support dates/times in the future?
> I've been trying some wakeup and reminder call scripts that rely on
> Touch to create a call file with a mtime value in the future. However,
> the calls are placed immediately. I'm suspecting BusyBox as the culprit.
>
> Tom
>
Tom,
You, sir, are correct:
BusyBox v1.00 (2005.06.29-07:42+0000) multi-call binary
Usage: touch [-c] FILE [FILE ...]
Update the last-modified date on the given FILE[s].
Options:
-c Do not create any files
I always use cron and run every five minutes to check for a flag file in
the /tmp directory (one that I create with something else, usually cron
too). It's not quite as fine resolution as you would have with this,
but it works.
Also, isn't it possible to specify the time of the call in the spool
file? I though I read/heard that somewhere...
--
Kristian Kielhofner
_______________________________________________
Astlinux-users mailing list
[email protected]
http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED].
_______________________________________________ Astlinux-users mailing list [email protected] http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
