On Wed, 13 Mar 2013, Aidan Van Dyk wrote: > kill -9 will absolutely prevent *minicom* from resetting the modem. > With kill -9 (-KILL), minicom is gone, it can't reset it. That's > the point of -KILL. i've tried this a number of times and have never had any success in leaving the modem in a usable state, even though the docs explicitly claim that a -9 kill should do this. > But as the kernel device is closed when minicom is killed, whatever > driver is responsible for it may be doing something... a hacky workaround i've been using is to simply leave minicom running, and manually remove the lock file (gack!). i hate doing that but, for now, at least it lets me test until i find a cleaner solution. > I know this is the whole "use the tool you know" thing, but it might > be better to use something intended for "scripting" serial ports, or > even fall back to setserial and if you don't like io in bash, expect > (or perl even if tk isn't your thing). > > If you want a shell script that talks to modems as an example, > HylaFAX uses shell for probing modems: > http://git.hylafax.org/HylaFAX?a=blob;f=etc/probemodem.sh.in;hb=master i would be more than happy to find a better utility than minicom, i'll check that out. i see RGB has also weighed in ... rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================