Problems with binkd for linux

[Mike Powell]

| MP> Right now, I am up to rc(5658)=11.
| MP>
| MP> Is there somewhere I can find out what these reason codes mean?
|
| Try searching for "rc(5658)=1" in the source code.
+-[ML=>MP]

I have. It did not show up anywhere. Actually, I don't think the number
in the () means anything anyway. It always changes, and seems to match
other numbers that show up on the screen during the session. It is the 11
that is significant, and I didn't see it anywhere in the code members I
looked at (there are many, so I didn't get through them all).

To be honest, I would have expected some better docs with the thing. If
you read what little is provided (and on the web), you'd think you never
get error codes because they aren't mentioned anywhere.

Mike

##MMR 2.61(beta). !link ML 01-13-10 03:07

[Mvan Le]

MP> other numbers that show up on the screen during the session. It is the 11
MP> that is significant, and I didn't see it anywhere in the code members I
MP> looked at (there are many, so I didn't get through them all).

Try increasing your loglevel to 100. Then check the logfile again after the
error occurs.

[andrew clarke]

On Wed 2010-01-13 19:24, Mike Powell (1:2320/105) wrote to Mvan Le:

| MP>> Right now, I am up to rc(5658)=11.
| MP>>
| MP>> Is there somewhere I can find out what these reason codes mean?
MP> |
MP> | Try searching for "rc(5658)=1" in the source code.

Your software's weird quoting mechanism using the pipe '|' symbol is not very
friendly towards most mail readers. Almost everybody uses the '>' symbol.

MP> I have. It did not show up anywhere. Actually, I don't think
MP> the number in the () means anything anyway. It always changes,
MP> and seems to match other numbers that show up on the screen during
MP> the session.

The number between the parentheses is the process ID. It will match the PID
displayed with the 'top' command in Linux/BSD, or the ID column in System ->
Administration -> System Monitor in Ubuntu (under the Processes tab).

MP> It is the 11 that is significant, and I didn't see it anywhere in
MP> the code members I looked at (there are many, so I didn't get
MP> through them all).

A return code of 11 could mean a segfault. So it could be that you've
discovered a bug that nobody else has encountered before. Hard to say without
further information though.

MP> To be honest, I would have expected some better docs with the thing. If
MP> you read what little is provided (and on the web), you'd think you never
MP> get error codes because they aren't mentioned anywhere.

Can you post your BinkD config file?

What do the BinkD logs say?