1. Forum
  2. FSXNet
  3. FSX MYS

  • FIDOPOLL logging in A46 despite not being invoked?

    From Zip@21:1/202 to g00r00 on Sunday, March 01, 2020 10:21:56
    Hello g00r00!

    I just noticed that FIDOPOLL still appears to do some logging (in the latest A46 prealpha) -- this is from my fidopoll.log for today:

    Mar 01 08:36:54 FIDOPOLL Version 1.12 A46 2020/03/01
    Mar 01 08:36:54 FIDOPOLL Version 1.12 A46 2020/03/01
    Mar 01 08:50:22 FIDOPOLL Version 1.12 A46 2020/03/01
    Mar 01 09:01:59 FIDOPOLL Version 1.12 A46 2020/03/01
    Mar 01 09:12:22 FIDOPOLL Version 1.12 A46 2020/03/01
    Mar 01 09:12:22 FIDOPOLL Version 1.12 A46 2020/03/01
    Mar 01 09:55:59 FIDOPOLL Version 1.12 A46 2020/03/01
    Mar 01 09:55:59 FIDOPOLL Version 1.12 A46 2020/03/01
    Mar 01 10:03:06 FIDOPOLL Version 1.12 A46 2020/03/01
    Mar 01 10:05:11 FIDOPOLL Version 1.12 A46 2020/03/01
    Mar 01 10:17:02 FIDOPOLL Version 1.12 A46 2020/03/01
    Mar 01 10:17:02 FIDOPOLL Version 1.12 A46 2020/03/01

    These log entries appear to correspond with MIS restarts (performed by me). Should it be logging anything if not invoked?

    (I have replaced all ./fidopoll calls with ./mis poll calls in my events and that seems to work fine.)

    Just curious! =)
    Thanks for the nice ongoing work on A46!

    Best regards
    Zip

    --- Mystic BBS v1.12 A46 2020/03/01 (Linux/64)
    * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)
  • From g00r00@21:1/108 to Zip on Sunday, March 01, 2020 17:17:36
    I just noticed that FIDOPOLL still appears to do some logging (in the latest A46 prealpha) -- this is from my fidopoll.log for today:

    (I have replaced all ./fidopoll calls with ./mis poll calls in my events and that seems to work fine.)

    Are you sure you have? Fidopoll can't log unless its being executed
    somewhere. I have no fidopoll.log in my log directory on my system.

    --- Mystic BBS v1.12 A46 2020/03/01 (Windows/64)
    * Origin: Sector 7 (21:1/108)
  • From Zip@21:1/202 to g00r00 on Sunday, March 01, 2020 11:29:30
    Hello g00r00!

    Thank you for your reply!

    On 01 Mar 2020, g00r00 said the following...
    Are you sure you have? Fidopoll can't log unless its being executed somewhere. I have no fidopoll.log in my log directory on my system.

    Ah -- I just found it -- I have "fidopoll KILLBUSY ALL" in my systemd unit file. :-D

    Is there any replacement for that one?

    Thanks again!

    Best regards
    Zip

    --- Mystic BBS v1.12 A46 2020/03/01 (Linux/64)
    * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)
  • From g00r00@21:1/108 to Zip on Sunday, March 01, 2020 17:53:04
    Ah -- I just found it -- I have "fidopoll KILLBUSY ALL" in my systemd
    unit file. :-D

    Is there any replacement for that one?

    No, because you should never be running that like you are. :)

    --- Mystic BBS v1.12 A46 2020/03/01 (Windows/64)
    * Origin: Sector 7 (21:1/108)
  • From Zip@21:1/202 to g00r00 on Sunday, March 01, 2020 13:58:30
    Hello g00r00!

    Thank you for your reply!

    On 01 Mar 2020, g00r00 said the following...
    Is there any replacement for that one?
    No, because you should never be running that like you are. :)

    I'm using it to avoid MIS not starting up in case of a power outage (where stale BSY files are left on disk). It is run by systemd before launching MIS. Actually I also run it after shutting down MIS (in case MIS would have
    crashed during shutdown and left some BSY files), although that scenario is less likely and should be covered by the removal on startup, so probably redundant.

    Perhaps there is some built-in functionality in MIS regarding the BSY files?

    I read about the 2-hour stale BSY file timeout the other day, but I'd rather start MIS quicker than that after a power outage. :)

    Best regards
    Zip

    --- Mystic BBS v1.12 A46 2020/03/01 (Linux/64)
    * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)