Hello Vince!

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.

Take care,
Gert

- Get the best with linux -

--- Msged/LNX 6.2.0 (Linux/2.6.39-gentoo-r1 (x86_64))
* Origin: KofoBBS at ftp://fido1.kofobbs.net (2:230/150)

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)

* 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.

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.

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))
* Origin: KofoBBS at ftp://ftp.kofobbs.dk (2:230/150)