Re: 'at' and queuing

[Alexander V. Lukyanov]

On Mon, Apr 18, 2005 at 06:44:48PM +1000, James Teh wrote:
> I missed it. (Btw, I didn't know about the 'at' command for a long time.
> Someone else has already requested that some help text be added for it
> (yanked from the man page perhaps?), but even inclusion in the list of
> commands obtained when help is called with no arguments would be great -
> it isn't listed there at all.)

The help screen with command listing is already full (24 lines, two commands
per line). To include all commands it has to be re-organized (e.g. list
commands without description, more than two per line, or make it longer than
24 lines).

> Currently, the 'at' command cannot be used with queues. Often, i have
> wanted to start the execution of a queue at a certain time with a
> sequence of commands such as the following:
> queue stop
> [a series of queue commands for the current site]
> at 2:15AM -- queue start
> Currently, this will not work. In this example, at 2:15AM, the 'at'
> command tries to start another queue which doesn't exist and therefore
> achieves nothing, rather than starting the queue defined earlier.

Try this instead of "queue stop":
        queue at 2:15AM

The at command will wait and prevent following commands execution.

> job). This would be neat for scheduling both the start and end times for
> queued transfers, which is nice for those of us who have off-peak
> bandwidth to burn. :-)

You can do this:

        repeat at 2:15AM -- set net:limit-total-rate 0 &
        repeat at 8:00AM -- set net:limit-total-rate 1000 &

So that at 2:15AM it will turn off rate limitation, and at 8:00AM it will
limit it to 1000 bytes per second. The only problem is to determine initial
rate limit.

> * Tab completion with 'at': Currently, tab completion works with queue
> for file names, etc., but not with 'at'. Adding this would be extremely
> useful.

Yes.

> * Additional commands to manipulate slots: As far as I can find, there
> is no command for listing slots nor removing a slot once it has been created. 
> (Actually, I just double checked and the man page does note that slot
> should list currently allocated slots, but I can't get this to work.
> Typing slot with no arguments does nothing.)

It does show slots with opened sessions.

-- 
   Alexander.