Linux-Hams archive - June 1997: Re: problem with netromd.

Re: problem with netromd.

Richard Adams (wmdklose.bbfldy@videotron.ca)
Tue, 3 Jun 1997 07:54:53 +0000 (GMT)

According to Carl Makin, While burning my cpu.:
>
>
> I've just upgraded to 2.0.30 with mod13a and axutils 2.1.37. Netromd
> works for a while (several hours I think) before generating an error in
> syslog like;
>
> "unable to write to /proc/net/nr_nodes"
>
> and nr_neigh. The box stops broadcasting routes. Debug messages in the
> syslog indicate netrom broadcasts are being received. "cat"'ing the
> netrom "files" in /proc/net shows them to be "empty".
>
> Any ideas?
>

I hope this is still valid, i think i am correct in saying that the
following patch will correct the problem. I had the same problem when i
upgraded also.

--- netromr.c.old Thu May 8 18:49:29 1997
+++ netromr.c Thu May 8 18:50:00 1997
@@ -74,12 +74,6 @@
return;
}

- if ((fp = fopen(PROC_NR_NEIGH_FILE, "r")) == NULL) {
- if (logging)
- syslog(LOG_ERR, "netromr: cannot open %s\n",
PROC_NR_NEIGH_FILE);
- close(s);
- return;
- }
fgets(neigh_buffer, 90, fp);

portcall = ax2asc(neighbour);

If you look at netromr.c you will notice that the above text is to be found
twice, hence the problem.

> Carl.
> 

-- 
Regards Richard, 73.              | "I see" said the blind man to his
AX25  pa3gcu@pi8mid.#zld.nld.eu   |  deaf en dumb daughter, who replyed,
smtp  pgwsoz.prja@omsoft.com      | "Yes" Linux AX25. NET/ROM, "I have heard
inet  ysa@mail.dy.fi |  that what you see is what you get".