[Thread Prev][Thread Next][Thread Index]
Re: Pilotmgr crashing for unknown reason
- To: Adam Stein <adam@xxxxxxxxxxxxxxxxxxxxxx>, pilotmgr@xxxxxxxxxxxxxxxxxxxxxxx
- Subject: Re: Pilotmgr crashing for unknown reason
- From: "Zuberi,A." <asimzuberi@xxxxxxxxxx>
- Date: Thu, 30 Jul 1998 15:42:15 -0500
- In-reply-to: Adam Stein <adam@iset.scan.mc.xerox.com> "Re: Pilotmgr crashing for unknown reason" (Jul 30, 12:48pm)
- Original-from: "Zuberi,A." <asim@xxxxxxxxxxxxxxxxx>
- Original-to: Adam Stein <adam@xxxxxxxxxxxxxxxxxxxxxx>, pilotmgr@xxxxxxxxxxxxxxxxxxxxxxx
- Original-to: Adam Stein <adam@xxxxxxxxxxxxxxxxxxxxxx>, pilotmgr@xxxxxxxxxxxxxxxxxxxxxxx
- References: <199807301948.PAA29054@chroma2.iset.scan.mc.xerox.com>
- Sender: owner-pilotmgr@moshpit
Hi there,
My settings are as follows; but the Pilotmgr still crashes!!!! The cradle is
connected to `ttyb`. I have tried several options within `admintool`, but
there wasn't any luck.
==============================================================================
[diy]-[asim]->eeprom | grep -i ignore-cd
ttyb-ignore-cd=false
ttya-ignore-cd=false
==============================================================================
[diy]-[asim]-> pmadm -l
zsmon ttymon ttyb u root /dev/term/b cI -
/usr/bin/login - 38400 ldterm,ttcompat ttyb login: - vt100 y #Terminal -
Hardwired
On Jul 30, 12:48pm, Adam Stein wrote:
> Subject: Re: Pilotmgr crashing for unknown reason
> 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 *
> ***********************************************************
>
>-- End of excerpt from Adam Stein
------------------------------------------------------------------------
***********************************************************
* This is a public mailing list! *
* Please do not publish Sun proprietary information here! *
* - - - - - - - - - - - - - - *
* http://www.moshpit.org/pilotmgr *
***********************************************************