Hello Gert!   
      
   Sunday November 16 2014 14:55, you wrote to me:   
      
    > 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.   
      
   If you can upgrade to latest v1.0.4 for the binkd fixes but to cover your   
   error.   
   That is because mbtask is NOT running which is normal on some distros not   
   starting a new app so you will need to force a start by (depending of distro)   
   running /etc/rc.d/init/mbsed start or if using startd running systemctl start   
   mbsed.service.   
      
   Failing those then reboot system which should start all of your services   
   including mbsed.   
      
      
      
      
   Vince   
      
   --- Mageia Linux v4/Mbse v1.0.4/GoldED+/LNX 1.1.5-b20120229   
    * Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)