Setting a job’s killtime without also setting the
time to send may cause the wrong value for the killtime to
be sent. This is because the killtime is calculated as the
difference in time between the killtime and time to send:
and if the time to send is not specified, then
faxalter uses the current time instead of querying
the server for the job’s time to send.
faxalter suspends a job before attempting to alter
its state. If a job is active when a suspend request is made
there may be a delay while waiting for the job to enter a
consistent state where it can be suspended. If
faxalter is interrupted during this time then jobs
may be left suspended.
faxalter requeues the job. This means that the job
will end up at the bottom of the queue for the job’s
priority. Thus, when queues are heavy an adjustment of the
job’s killtime may need to be considered when altering
any other parameter.
faxalter only understands how to alter a subset of
the available job parameters; there are many more
client-controllable parameters that can only be modified by
communicating directly with the server using the underlying
protocol.
The continued use of the at(1)-style notation for
specifying times is questionable (it was done for backwards
compatibility).
|