Re: [hpoj-devel] ptal-mlcd and hotplug scripts

[Allen B. <ba...@lo...>]

David Paschal wrote:
> 
> Specifically, I added a "-hotplug" switch, which tells ptal-mlcd to
> "activate" (establish communication with the peripheral) right away at
> startup, and to attempt to re-activate after a deactivation (loss of
> communication with the peripheral, which could be caused by an unplug or
> power-down of the peripheral or by a protocol error).  If an activation
> or re-activation ever fails (presumably due to an unplug or power-down),
> then ptal-mlcd exits.

I tried unplugging and replugging my USB cable a few times and it seems
to work OK. (Subject to my USB hardware performing properly; I'm afraid
my 3 year old DELL Dimension is wearing out.) The only problem I have
with this setup is that my hotplug script starts both ptal-mlcd and
ptal-printd, but only ptal-mlcd exits automatically. So, each replug
starts another ptal-printd. Would it be possible for ptal-printd to
receive notification from ptal-mlcd that ptal-mlcd is shutting itself
down?

> I also haven't yet fixed the bug related to the lack of standard
> input/output/error file descriptors when run from a hotplug script, so
> the "</dev/null" workaround is still necessary.

Would it be practical to add a SYSLOG output option to your utilities?

On another subject altogether: should 'ptal-hp scan' work with the G85?
I get the error message:

Scan upload state is 2 (i=11)!

Thanks,
Allen