Kevin Mark wrote:
On Wed, Feb 22, 2006 at 04:43:48PM -0600, Hugo Vanwoerkom wrote:
Kevin Mark wrote:
On Tue, Feb 21, 2006 at 10:07:15PM -0500, Hal Vaughan wrote:
On Tuesday 21 February 2006 17:41, Mike McCarty wrote:
Hal Vaughan wrote:
[snip]
Thanks, again, for your quick response. It's wo
On Wed, Feb 22, 2006 at 04:43:48PM -0600, Hugo Vanwoerkom wrote:
> Kevin Mark wrote:
> >On Tue, Feb 21, 2006 at 10:07:15PM -0500, Hal Vaughan wrote:
> >>On Tuesday 21 February 2006 17:41, Mike McCarty wrote:
> >>>Hal Vaughan wrote:
> >>>
> >>>[snip]
> >>>
> >>Thanks, again, for your quick response.
Kevin Mark wrote:
On Tue, Feb 21, 2006 at 10:07:15PM -0500, Hal Vaughan wrote:
On Tuesday 21 February 2006 17:41, Mike McCarty wrote:
Hal Vaughan wrote:
[snip]
Thanks, again, for your quick response. It's working now, which means I get
to sleep tonight and don't have to be at the computer a
On Wednesday 22 February 2006 03:54, Kevin Mark wrote:
> On Tue, Feb 21, 2006 at 10:07:15PM -0500, Hal Vaughan wrote:
> > On Tuesday 21 February 2006 17:41, Mike McCarty wrote:
> > > Hal Vaughan wrote:
> > >
> > > [snip]
> >
> > Thanks, again, for your quick response. It's working now, which means
On Tue, Feb 21, 2006 at 10:07:15PM -0500, Hal Vaughan wrote:
> On Tuesday 21 February 2006 17:41, Mike McCarty wrote:
> > Hal Vaughan wrote:
> >
> > [snip]
> >
>
> Thanks, again, for your quick response. It's working now, which means I get
> to sleep tonight and don't have to be at the computer
Hal Vaughan wrote:
On Tuesday 21 February 2006 22:37, John Hasler wrote:
Hal Vaughan writes:
Does kill look for lock files and release devices?
No. Kill just sends a signal (default SIGTERM). Minicom catches the
signal, cleans up by closing files and restoring the terminal settings and
th
On Tuesday 21 February 2006 22:37, John Hasler wrote:
> Hal Vaughan writes:
> > Does kill look for lock files and release devices?
>
> No. Kill just sends a signal (default SIGTERM). Minicom catches the
> signal, cleans up by closing files and restoring the terminal settings and
> then exits. So
Hal Vaughan writes:
> Does kill look for lock files and release devices?
No. Kill just sends a signal (default SIGTERM). Minicom catches the
signal, cleans up by closing files and restoring the terminal settings and
then exits. Sounds like it restores the serial port settings as well. Try
'kil
On Tuesday 21 February 2006 17:41, Mike McCarty wrote:
> Hal Vaughan wrote:
>
> [snip]
>
> > Now whenever a program ends, or if I kill a program (so it doesn't have
> > time to exit), I can tell by watching the modem that it hangs up
> > immediately (the carrier detect led goes off instantly, along
On Tuesday 21 February 2006 17:41, Mike McCarty wrote:
> Hal Vaughan wrote:
>
> [snip]
>
> > Now whenever a program ends, or if I kill a program (so it doesn't have
> > time to exit), I can tell by watching the modem that it hangs up
> > immediately (the carrier detect led goes off instantly, along
Hal Vaughan wrote:
[snip]
Now whenever a program ends, or if I kill a program (so it doesn't have time
to exit), I can tell by watching the modem that it hangs up immediately (the
carrier detect led goes off instantly, along with the clear-to-send light).
I'd think this was a Perl problem,
I set up my system to use Sarge because of the reputation for Debian
stability. Now, ever since I updated my system with "aptitude upgrade" it
won't work and this is causing a SERIOUS problem. I've never liked posts
that say, "NEED HELP", or "URGENT" in the subject, but I do need help
figurin
12 matches
Mail list logo
