pcmcia-cs latest update "bad file descriptor" error

[Rod Haper]

Dexter Ang wrote:
> On Tue, 12 Oct 2004 14:13:48 -0500, Rod Haper <rhaper at houston.rr.com> wrote:
> 
>>No problem on my Dell Inspiron 8100 with a LinkSys EtherFast 10/100+56K
>>Modem PC Card.
>>
>>Rod
> 
> 
> Hi Rod,
> 
> Can you confirm that there is no error message when you start
> /etc/rc.d/init.d/pcmcia from the command line? If so, could you also
> post in the bugzilla entry at:
> 
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=135508
> 
> And state that you are using a Dell Inspiron 8100. It might only be
> related to Thinkpads.
> 
> dex
> 

Hello, Dex,

Well, now I'm also getting the error.  I don't know why I didn't get it 
yesterday after updating to pcmcia-cs-3.2.7-1.8.2.1.  After reading the 
OP's message, I ran /etc/rc.d/init.d/pcmcia to stop and start the 
service and did not get the error.  I even checked the /var/messages log 
file and there was no error message.  I don't understand why not.  This 
was definitely after the update.

I just reran /etc/rc.d/init.d/pcmcia again this morning after reading 
your message above and bang - I get the error message:

"Starting PCMCIA services: cardmgr[3630]: open_sock(socket 2) failed: 
Bad file descriptor"

I checked /var/messages and there was the error message.  BUT there was 
no error message from when /etc/rc.d/init.d/pcmcia ran at boot time when 
I booted my laptop this morning!  Strange.  I rebooted and checked 
/var/messages again and there was no error message.  I stopped and 
restarted pcmcia manually again with /etc/rc.d/init.d/pcmcia and got the 
error message on the command line and in /var/messages.  Mabye this 
behavior gives a clue.

Ayway, bottom line is if I now restart the pcmcia service manually, I 
too get the socket error but apparantly not when it runs at boot time. 
My network/serial PCMCIA card does seems to function normally however. 
Sorry for the confusion.

Rod