On Sat, Jun 24, 2006 at 09:06:07AM +0200, Giuseppe Sacco wrote:
> The provided patch doesn't apply to current code as this code was
...
> error echoing, and making it not die so easily.
ok
>
> The return codes that Paolo used didn't make sense to me, so I made and
well, basically I wanted to ha
On Thu, Jun 01, 2006 at 08:40:54AM +0200, oopla wrote:
> I should add that such jobids are from 'faxstat -s' with status 'W'.
did not see other fax in 'W' state, so couldn't really test in with 4.3.0.
But at least works on 'B', 'S'. On 'F' it bails out on failed JSUSP
('job already done').
> Al
I should add that such jobids are from 'faxstat -s' with status 'W'.
faxrm(1) fails as well on such jids, so it seems they're stale or
'phantoms'.
Anyway, from such faxstat(1), faxalter(1), faxrm(1) I get quite confused.
Also, note that although faxalter fails on JSUSP it exits with status 0
and
Package: hylafax-client
Version: 1:4.2.1
Severity: important
hi,
faxalter(1) seems unable to re-schedule a job.
This might actually be a bug in the server
E.g.:
job 5776 has timed out, exceeding max -k time of sendfax(1), hance it's in
queue with state W. Now I want to send it:
$ faxalter -v -a
4 matches
Mail list logo
