[ minicom-Bugs-301264 ] capture file not being flushed

[noreply@alioth.debian.org]

Bugs item #301264, was opened at 2005-03-17 01:18
You can respond by visiting: 
http://alioth.debian.org/tracker/?func=detail&atid=100031&aid=301264&group_id=30018

Category: None
Group: None
>Status: Closed
Resolution: None
Priority: 5
Submitted By: Nobody (None)
Assigned to: Nobody (None)
Summary: capture file not being flushed

Initial Comment:
Hi --

I am experiencing a problem where the capture file is not being completely written to disk.  The result is that the last segment {up to 4096 characters} is not captured, although it displays correctly on the screen.  My typical "session captures" generate files 36k and larger.

I am getting the same result with minicom version 2.00.0 (compiled Jan 25 2003) running on Red Hat Linux sii002 2.4.20-20.9 #1 Mon Aug 18 11:45:58 EDT 2003 i686 i686 i386 GNU/Linux and minicom version 2.1 (compiled Jun 15 2003) running on Linux 192.168.0.35 2.6.3-7mdk #1 Wed Mar 17 15:56:42 CET 2004 i686 unknown unknown GNU/Linux

--Rich

----------------------------------------------------------------------

>Comment By: Adam Lackorzynski (al-guest)
Date: 2005-03-24 23:51

Message:
Logged In: YES 
user_id=104

I've fixed that in CVS. The capture file is now flushed for
every write.


----------------------------------------------------------------------

Comment By: Nobody (None)
Date: 2005-03-24 23:41

Message:
Logged In: NO 

The problem is resolved by setting last lines of script to execute a couple of shell commands rather than an *exit*  statement.  For example: 

! /bin/sync
sleep 5
! /usr/bin/killall -15 minicom

Signal 15; SIGTERM forces minicom to exit via the hangsig() function.  The sync may not actually be required and it may not be necessary to delay between the sync and the killall.  That is how I am doing it, and it works.  

In minicom.c there are two exit points.  One is via hangsig() the other is via ctrl-a X with quit==RESET.  One difference between the two is that the latter does not call hangup() nor does it reset the modem via modemreset() {both in dial.c}.


----------------------------------------------------------------------

You can respond by visiting: 
http://alioth.debian.org/tracker/?func=detail&atid=100031&aid=301264&group_id=30018