proposed mheardd and mheard patches
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): 005301c57fa4$0b35da90$0700010a@jeanpaul
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Chuck,
As you noticed, a number of ROSE / FPAC stations have difficulties with the mheard function and cannot display AX25 traffic statistics.
This is because mheard does not find mheard.dat database file.
This can occure if :
- the directory, where mheard.dat file should be, does not exist. (It is usually in /var/ax25/mheard/ )
- or mheard.dat is written into another directory.
In the first case, presently, mheardd does not complain if /var/ax25/mheard/ directory has not been created before it is started. This is probably a default in the make install procedure of ax25-tools and could be corrected.
However, I thought it would be more user friendly if both programs where more verbous when finding errors.
Thus, I made two small patches.
With the first one, mheardd will display the directory and file when the daemon fails to write mheard.dat file. If so it will exit. User will know the directory to mkdir before starting mheardd again.
Modified mheard client, will also display the directory and file names if it does not find it.
The user will thus be able to understand the situation and solve it.
Proposed patch is here :
http://f6bvp.free.fr/logiciels/fpac/mheardd.diff
73 de Bernard, f6bvp
Quoted 5 lines · Bernard Pidoux
Chuck,
As you noticed, a number of ROSE / FPAC stations have difficulties with the mheard function and cannot display AX25 traffic statistics.
Quoted 7 lines
This is because mheard does not find mheard.dat database file.
This can occure if :
- the directory, where mheard.dat file should be, does not exist. (It is usually in
/var/ax25/mheard/)
- or mheard.dat is written into another directory.
Exactly it is in another directory, seems that there is not continuity with some of this stuff.
Well I know why mine is not working when I updated the ax25-apps it appears the latest update now puts the mheard.dat file in the following location/var/lib/ax25/mheard/mheard.dat
So I went in and created a symlink in the /var/ax25/mheard directory pointing at the /var/lib/ax25/mheard/mheard.dat
NOW I have mheard working. I thought I looked at that the other day but looks like I did not, that was another one of those late night/early morning things... You know about that...
Quoted 6 lines
In the first case, presently, mheardd does not complain if
/var/ax25/mheard/directory has not been created before it is started. This is probably a default in the make install procedure of ax25-tools and could be corrected.
The first thing I do after the ax25 stuff is up and running and I can see what is going on the listen screen is do a mheard. That will tell me right then and there if it is writing to somewhere the client can see.
Quoted 2 lines
However, I thought it would be more user friendly if both programs where more verbous when finding errors.
I agree, indeed I would also like to see fpac complain more loudly if it does not find things where they should be, but one step at a time.
Quoted 7 lines
Thus, I made two small patches.
With the first one, mheardd will display the directory and file when the daemon fails to write mheard.dat file. If so it will exit. User will know the directory to mkdir before starting mheardd again.
This is very good, because I know that FPAC is looking for the mheard data in the /var/ax25/mheard/mheard.dat so worse case can create a symlink and get it on line correctly.
Quoted 2 lines
Modified mheard client, will also display the directory and file names if it does not find it.
Again very good, because what happened this last time around was that it moved the target location.
Quoted 5 lines
The user will thus be able to understand the situation and solve it.
Proposed patch is here :
http://f6bvp.free.fr/logiciels/fpac/mheardd.diff
Yes, I will try to apply it if possible tonight, if not I wil do so during the week.
Signature · 5 lines
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."