Ok, so I'm now running the BBS on 64bit ubuntu linux. Previously I've been running on Raspbian off of a RPiB3. I've always ran MIS and MIS2 under the
old install. When I tried to run MIS in x64 (not armhf), I noticed a surprising event. I found that I would eventually see two instances of MIS running.

I would start it with 'sudo ./mis -d' and it would run fine. Then later I would try to connect and it would fail. I'd do a 'ps -ef | grep mis' and
then I would see two instances of MIS. One would be owned by init (process
#1) and the second would be a child of the first. This would consistently happen. I decided this was a good time to try MIS2 and have been running it without incident for at least a day now.

Has anybody else seen this behavior?

Ò Ö· Ò .
Ö·Ò·ÒÖÖ·Ç·Ö·Ò· Ö·Ç ÖÄÖÖÇ·Ö·Ò·ÒÒÒ cyberia.darktech.org
ӶРӶǽÐÐÓ½ÐÐ Ó½Ó ÓÄÓ¶Ó½ÓÄÐ ÐÓÐ San Jose, CA.
Ó½ ½Ó ½

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 07/20/17, Gryphon said the following...

Ok, so I'm now running the BBS on 64bit ubuntu linux. Previously I've been running on Raspbian off of a RPiB3. I've always ran MIS and MIS2 under the old install. When I tried to run MIS in x64 (not armhf), I noticed a surprising event. I found that I would eventually see two instances of MIS running.

I would start it with 'sudo ./mis -d' and it would run fine. Then later
I would try to connect and it would fail. I'd do a 'ps -ef | grep mis' and then I would see two instances of MIS. One would be owned by init (process #1) and the second would be a child of the first. This would consistently happen. I decided this was a good time to try MIS2 and
have been running it without incident for at least a day now.

Has anybody else seen this behavior?

I have...exactly like that. It was happening to me on Ubuntu 16.04 LTS
server (32 bit). I started running MIS2 for telnet and kept MIS for BINKP
and events. Like your's, when I did that, it stopped MISbehaving ;)

Thanks!
Orbitman (Allen)
telnet://orbitbbs.ddns.net:7210
Opp, Alabama, USA

--- Mystic BBS v1.12 A34 (Linux/32)
* Origin: Orbit BBS--telnet:orbitbbs.ddns.net:7210 (AL) (21:2/131)

On 07/20/17, Gryphon said the following...

Ok, so I'm now running the BBS on 64bit ubuntu linux. Previously I've been running on Raspbian off of a RPiB3. I've always ran MIS and MIS2 under the old install. When I tried to run MIS in x64 (not armhf), I noticed a surprising event. I found that I would eventually see two instances of MIS running.

I would start it with 'sudo ./mis -d' and it would run fine. Then later
I would try to connect and it would fail. I'd do a 'ps -ef | grep mis' and then I would see two instances of MIS. One would be owned by init (process #1) and the second would be a child of the first. This would consistently happen. I decided this was a good time to try MIS2 and
have been running it without incident for at least a day now.

Has anybody else seen this behavior?

I was having that issue with A34 as well. At one point I had 4 instances of MIS running. I'm running 32 bit instead of 64 if it matters.

Immortal

--- Mystic BBS v1.12 A33 (Linux/32)
* Origin: Lightning BBS -- lightningbbs.com:2400 (21:1/185)

On 07/19/17, Orbitman pondered and said...

On 07/20/17, Gryphon said the following...

Ok, so I'm now running the BBS on 64bit ubuntu linux. Previously I'v been running on Raspbian off of a RPiB3. I've always ran MIS and MIS under the old install. When I tried to run MIS in x64 (not armhf), I noticed a surprising event. I found that I would eventually see two instances of MIS running.

I would start it with 'sudo ./mis -d' and it would run fine. Then la I would try to connect and it would fail. I'd do a 'ps -ef | grep mi and then I would see two instances of MIS. One would be owned by ini (process #1) and the second would be a child of the first. This woul consistently happen. I decided this was a good time to try MIS2 and have been running it without incident for at least a day now.

Has anybody else seen this behavior?

I have...exactly like that. It was happening to me on Ubuntu 16.04 LTS server (32 bit). I started running MIS2 for telnet and kept MIS for
BINKP and events. Like your's, when I did that, it stopped MISbehaving ;)

Ok. Glad to know it wasn't just me. I use MIS2 now for both telnet and
binkp. But I use MIS for only ftp. I've noticed that MIS stays up and is
only one instance when I don't run telnet on it. I suspect that there's some user event that is causing the issue with telnet on MIS. I.e. the script kiddie callers are doing someting to make it happen.

Ò Ö· Ò .
Ö·Ò·ÒÖÖ·Ç·Ö·Ò· Ö·Ç ÖÄÖÖÇ·Ö·Ò·ÒÒÒ cyberia.darktech.org
ӶРӶǽÐÐÓ½ÐÐ Ó½Ó ÓÄÓ¶Ó½ÓÄÐ ÐÓÐ San Jose, CA.
Ó½ ½Ó ½

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)