• mis problem, likely exists in xurrent a18 does exist in a17

    From Bcw142@46:1/138 to G00r00 on Friday, June 10, 2016 08:33:16
    Mystic problem in A17, I just found mis wasn't running and my experimental board wasn't up. Why? your new mis.bsy exists in Semaphore and YES it was in daemon mode. In this case it was under x64 Linux, Here's what I saw: bcw@leno:/mystic$ ps aux | grep mis
    bcw 3333 0.0 0.1 322632 5440 ? Sl Jun09 0:01 /usr/lib/telepathy/mission-control-5
    bcw 10787 0.0 0.0 15948 2200 pts/10 S+ 09:15 0:00 grep --color=auto mis
    bcw@leno:/mystic$ sudo ./mis -d
    [sudo] password for bcw:
    MIS is already running (mis.bsy exists in Semaphore directory) bcw@leno:/mystic$ ps aux | grep mis
    bcw 3333 0.0 0.1 322632 5444 ? Sl Jun09 0:01 /usr/lib/telepathy/mission-control-5
    bcw 10796 0.0 0.0 15948 2164 pts/10 S+ 09:15 0:00 grep --color=auto mis

    So not only wasn't the BBS up, but I couldn't put it up!
    bcw@leno:/mystic$ ls semaphore
    mis.bsy
    bcw@leno:/mystic$ rm semaphore/*
    rm: remove write-protected regular empty file semaphore/mis.bsy? y
    Then I got mis to work. There needs to be some type of crash recovery as well as a way to deal with normal shutdowns (which is what led to this).

    --- Mystic BBS v1.10 (Linux)
    * Origin: Orbit BBS - Opp, AL USA | orbitbbs.ddns.net (46:1/138)
  • From g00r00@46:1/127 to Bcw142 on Saturday, June 11, 2016 23:41:05
    Then I got mis to work. There needs to be some type of crash recovery as well as a way to deal with normal shutdowns (which is what led to this).

    There are already all of those things in place. I am not sure what you're trying to say, ask, or suggest here?

    --- Mystic BBS v1.12 A19 (Windows)
    * Origin: Sector 7 [Mystic BBS WHQ] (46:1/127)