On 07/28/2017 03:32 PM, Chris Adams wrote:
Once upon a time, Tom Horsley <horsley1953@xxxxxxxxx> said:
I've noticed a tendency for my ttyACM0 device to show
up a ttyACM1, ttyACM2, etc. if I unplug and plug it
back in. Perhaps something similar happens to ttyUSB0?
If you unplug the adapter while the device is still open (something is
still connected, like screen, minicom, etc.), the kernel can't free the
device. So if the software is still running and you plug it back in,
it'll get the first available device.
Usually, if you close the software before plugging back in, the device
will be freed and available (but there are some cases where I've seen
the device "stuck").
When I unplug the USB/TTY dongle, screen terminates as /dev/ttyUSB0 went
away.
In the past (say 3 months ago), I would unplug, watch screen terminate,
plug back in, see ttyUSB0 reappear and screen work just fine.
This is a recent development. I noticed it back in late June, but it
had to focus on getting all my docs ready for the conferences. Now that
I am back, I have the time to do some more arm work, and have to deal
with this problem.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
