From: Chuck Hast <wchast@gmail.com>
To: Bernard Pidoux <pidoux@ccr.jussieu.fr>
Cc: List for LINUX ROSE/FPAC network switch <fpac@f6fbb.org>,
fpac@home.f6fbb.org, John Hurst <jhurst@utac.net>,
Linux-Hams <linux-hams@vger.kernel.org>
Subject: Re: [fpac] Re: ax25ipd issue
Date: Mon, 13 Jun 2005 05:19:57 -0600 [thread overview]
Message-ID: <620c905705061304194a4f53ee@mail.gmail.com> (raw)
In-Reply-To: <42AD56D0.6050705@ccr.jussieu.fr>
On 6/13/05, Bernard Pidoux <pidoux@ccr.jussieu.fr> wrote:
> Chuck Hast a écrit :
> > Bernard,
> > Does double ax25ipd command at the bottom start up two instances of
> > ax25ipd? Also I believe that the -l4 is log level 4 correct?
>
> No, It starts only one instance of ax25ipd.
> The second call is in case ax25ipd will not be able to connect
> immediately to remote ip stations, it only gives it a second chance.
> Otherwise, the system would have to wait for one more hour until the
> script starts again.
Ahh, now I understand.
>
> By the way, I had to introduce a small patch into ax25ipd source code
> for it would fail if a LAN connexion through UDP port is not reachable,
> All the AXIP system would lock and thus FPAC.
>
> The patch is in io_error() routine.
>
> exit(2);
> } else if (mode == UDP_MODE) {
> syslog(LOG_ERR, "reading from udp socket,
> %s\n", strerror(errno));
> // perror("reading from udp socket");
> // exit(2);
> } else if (mode == TTY_MODE) {
>
> In case of read error, ax25ipd will keep on trying to read, instead of
> aborting.
>
>
OK, I shall find the source and add this to it so that the problem will be
corrected.
--
Chuck Hast
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going
out and having to identify your bits and pieces in the midst of torn
and twisted metal."
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2005-06-13 11:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-11 13:38 ax25ipd issue Chuck Hast
2005-06-11 15:41 ` John Hurst
2005-06-12 19:05 ` Bernard Pidoux
2005-06-12 21:37 ` Chuck Hast
2005-06-13 9:50 ` [fpac] " Bernard Pidoux
2005-06-13 11:19 ` Chuck Hast [this message]
2005-06-11 19:43 ` Tomi Manninen
2005-06-11 19:54 ` Jeremy Utley
2005-06-11 20:09 ` Tomi Manninen
2005-06-11 20:19 ` John Hurst
2005-06-11 20:32 ` David D. Hagood
2005-06-11 20:51 ` Chuck Hast
2005-06-11 20:45 ` Chuck Hast
2005-06-23 11:51 ` Steve Fraser
2005-06-23 12:15 ` Chuck Hast
2005-06-23 16:13 ` Bernard Pidoux
2005-06-11 23:03 ` Steve Fraser
2005-06-12 4:50 ` Jeremy Utley
2005-06-12 14:24 ` Tomi Manninen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=620c905705061304194a4f53ee@mail.gmail.com \
--to=wchast@gmail.com \
--cc=fpac@f6fbb.org \
--cc=fpac@home.f6fbb.org \
--cc=jhurst@utac.net \
--cc=linux-hams@vger.kernel.org \
--cc=pidoux@ccr.jussieu.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox