Re: Problems running PilotManager

[Casper Dik <casper@holland>]

>I could "solve" my problem. I tried everything I could think of - new
>installations of perl, pilotmgr, booting (and switching off) the
>workstation. Then I moved the craddle from b to a and now it works
>again. Funny is, that both devices look absolutely identical:
>crw-rw-rw-   1 root     sys       29,  0 May 15 14:05 zs@0,100000:a
>crw-rw-rw-   1 uucp     operator  29,131072 Feb 26  1997
>zs@0,100000:a,cu
>crw-rw-rw-   1 root     sys       29,  1 May 11 16:27 zs@0,100000:b
>crw-rw-rw-   1 uucp     operator  29,131073 Feb 26  1997
>zs@0,100000:b,cu
>how would one create these devices from scratch - would that help?
>	Rudolf


The segmentation fault happens when pilot manager fails to open the
device.

Since you're using the cua (Call-out) devices, a failure can
occur when the device is configured for "hardwire; soft carrier".

Try typing pmadm -l and see if there's a difference between the ttya and 
ttyb configs.

Casper

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