Re: Pilotmgr crashing for unknown reason

[Adam Stein <adam@xxxxxxxxxxxxxxxxxxxxxx>]

I do know of one cause for PilotManager to crash.  This is when it's crashing
when trying to connect to the pilot (when it's doing a socket() call).  This
happens when the Sun eeprom setting for the serial port has the ignore-cd
flag set to "true".  In order to connect to the pilot, the ignore-cd
attribute for the serial port MUST be set to "false".  Since the pilot isn't
on when PilotManager begins to connect, there never will be a carrier detect
signal, and so the socket() call goes down in flames.  A modem on the same
port can also work with the ignore-cd option set to false, so you don't have
to worry about that.

I spent 2 weeks finding this one.  I had PilotManager working in Solaris 2.5.
I upgraded to Solaris 2.6 and used admintool to configure the serial port
for my modem.  I have both devices hooked to the one serial port (I don't
have an AB cable) with a switchbox.  Modem worked create, but PilotManager
crashed.  Don't know what switched the eeprom's settings, the upgrade or
admintool.

Hope this helps.  Maybe this info should go into the "serial port FAQ" on
the PilotManager page?  I see they talk about admintool settings.  This could
compliment that.

                                                Adam
--
Adam Stein @ Xerox Corporation       Email: adam@xxxxxxxxxxxxxxxxxxxxxx
                                            
Disclaimer: All views expressed             
here have been proved to be my own.  [http://www.csh.rit.edu/~adam/]


------------------------------------------------------------------------
***********************************************************
*             This is a public mailing list!              *
* Please do not publish Sun proprietary information here! *
*        -  -  -  -  -  -  -  -  -  -  -  -  -  -         *
*             http://www.moshpit.org/pilotmgr             *
***********************************************************