* Reply to message originally in area CarbonArea

Hello Vince!

Sun Nov 16 2014, Vince Coen wrote to Gert Andersen:


 >> I have now got a old linux amd64 up and running to replace a old
 >> install of linux 64bit there have bad things and got my to work with a
 >> new newest kernel and then tried to install mbsebbs-1.0.1 first where
 >> it started up and just not got on network use by there not have been
 >> any working network address in use or like to work. Then I now got the
 >> real network and ip + hostname on the pc and then begain mbsebbs to
 >> come up with socket error ad mtask shows in it log file 'bad file^
 >> descriptor' and I am not sure if it is mbse or linux there do this.

 >> And where the error come out from.

 VC>If you can upgrade to latest v1.0.4 for the binkd fixes but to cover 
 VC>your
 VC>error.
 VC>That is because mbtask is NOT running which is normal on some distros 
 VC>not
 VC>starting a new app so you will need to force a start by (depending of 
 VC>distro)
 VC>running /etc/rc.d/init/mbsed start or if using startd running systemctl 
 VC>start
 VC>mbsed.service.

 VC>Failing those then reboot system which should start all of your 
 VC>services
 VC>including mbsed.

Hmm... I have xinetd and init.d/mbsebbs there should manage, but first got
my old mbsebbs there were reinstalled start to try to run but report error
by the ip and hostname not was right and I know this was in reason of the
nwetwork then not was there, but after I now got the network to works on
the pc stopped mbsebbs-1.0.1 to have problem as descriped and I upgraded to
1.0.4


  Take care,
            Gert

      - Get the best with linux - 

--- Msged/LNX 6.2.0 (Linux/2.6.39-gentoo-r1 (x86_64))