summaryrefslogtreecommitdiffstats
path: root/call/call.c
Commit message (Collapse)AuthorAgeFilesLines
* fix: on read through closed pipe, call did endless select(),Thomas Osterried2009-08-241-16/+59
| | | | | | | | read() = 0, wht consumed 100% CPU power. New options: -W: waits after EOF on stdin. Useful for scripting, for waiting for data coming via fd 3 (ax25 connection) -T secs: idle timout after secs seconds.
* Remove use of backwards compatibility header name.Ralf Baechle2009-06-211-12/+0
| | | | | | Glibc as old as 2.2 provides working headers under the right name and if not libax25 would install headers under the right name so this has become redundant and ugly.
* Fix build error caused by variable definition after statement.Ralf Baechle2009-06-061-1/+2
|
* fixed segfault issueThomas Osterried2009-04-151-10/+10
|
* call writes messages to stdout using printf(). it writes dataThomas Osterried2009-03-191-8/+33
| | | | | | | | | | | from the ax25 connection using write(0). everything was fine as long as call wrote to stdout. If instead we use output redirection to a file or stdout (> foo, | bar), then the messages like "Connected to.." appeared at the end of the connection. I guess it's a glibc issue that printf (whih is buffered) behaves different when stdout is redirected. Fixed using fflush() after each printf().
* removed debug codeThomas Osterried2009-01-251-2/+0
|
* fixed segfault issue by parsing unexpected bin headers.Thomas Osterried2009-01-251-28/+39
|
* revised linemodeThomas Osterried2009-01-241-33/+1
|
* Hope this is the last fix for the slightly corrupted outputThomas Osterried2009-01-241-6/+12
| | | | issue whenever a packet ended with "\r ".
* major fix.Thomas Osterried2009-01-241-37/+101
| | | | | | | | | | | | | | 1. if a line was split over two ax25 packets, we read i.e. 1. "foobar told me" 2. " go7+. ". The second packet was interpreted like starting with " go7+. ". thus in a pure bbs listing it was misinterpreted as start of a 7plus file. Since the data was not like a 7plus header starts, the 7plus download parser caused a segfault (after copying i.E. 1555 bytes to char s[20]. [seen in gdb ;-] -> enforced a "linemode". 2. protocol and array size assurances in the #BIN and 7plus part, as well as in dupdstatw().
* small fixThomas Osterried2009-01-241-0/+3
|
* smaller fixesThomas Osterried2009-01-241-9/+8
|
* fix for fix in dos to unix time conversion partThomas Osterried2009-01-241-1/+1
|
* fixed problem i produced yesterday.Thomas Osterried2009-01-241-3/+5
| | | | | currently we've seen other bugs in call which lead to malfunctions and segfaults.
* smaller changes.Thomas Osterried2009-01-231-15/+16
|
* fixed bin download corruption.Thomas Osterried2009-01-221-29/+35
| | | | fixed dos to unix time conversion.
* #BIN upload now preserves the file time.Thomas Osterried2009-01-221-2/+25
|
* - bugfixes:Thomas Osterried2009-01-211-57/+84
| | | | | | | | | | | | - fileupload (in raw and gui "slave" mode) goes only step by step the 128 bytes further if user enters a character. Thanks to Daniel DO8CD for the report. - write() returns -1 at EAGAIN (packet links are usually slower then linux file IO, and EAGAIN occurs because the txbuffer in the kernel is full). This lead to a bad substraction in sent bytes and thus to file corruption at the receiving site. - added more help: now explaining all the ~-Escapes in raw mode in the ~? command.
* - new option -S: be silent. useful for using call in shellscripts.Thomas Osterried2008-07-091-12/+29
| | | | | | - call was not usable as a pipe in scripts because it read 511 bytes, tried to write these 511 bytes (but 256 is max for ax25 I-frames), got -1 EMSGSIZE (Message too long) and terminated.
* the following issues are fixed:Thomas Osterried2008-04-131-2/+14
| | | | | | | | | | | | | | | 1. if stdin closes (i.e. if call is right end of a pipe), then call should close. this also fixes the case when call reads from a unix fifo, and the other end of the fifo terminates. This produced highest cpu-load, with select(), read() = 0, select(), read() = 0, .. 2. if stdin is not a tty, i.e. call is called from ax25d, then it's not a good idea to honor the ~ commands. In that special case, you could imagine what ~! means, while ax25d is running as uid 0... 3. while not operating on pty, the FILE buffers are not flushed in all cases. Thus, the messages like "Connected .." were be printed in the termination phase of the program..
* Changed STD_DWN_DIRThomas Osterried2006-10-041-1/+1
|
* - New option "-s <sourcecall>" (like in ax25_call)Thomas Osterried2005-12-281-7/+14
| | | | - usage: new function usage()
* updated libtool, uniformly indented source, corrected small ax25mond ↵Terry Dawson VK2KTJ2001-09-121-1633/+1858
| | | | Makefile bug
* Initial revisionax25-apps-0.0.5p2Craig Small2001-04-101-0/+5
|
* Import ax25-apps 0.0.4 from tarballax25-apps-0.0.4Ralf Baechle1999-08-241-5/+7
|
* Import ax25-apps 0.0.3 from tarballax25-apps-0.0.3Ralf Baechle1999-08-101-1/+13
|
* Import ax25-apps 0.0.1 from tarballax25-apps-0.0.1Ralf Baechle1999-06-071-0/+1941