Mail Import / Export and Events don't appear to trigger automatically when using the daemon under linux. Is this a misconfiguration on my part or am I supposed to run them as Linux Cron Jobs?

- Mike

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Arcadia BBS | Connecticut USA | bbs.arcadiabbs.com (21:3/107)

Hello Nazferiti!

On 08 May 2020, Nazferiti said the following...

Mail Import / Export and Events don't appear to trigger automatically
when using the daemon under linux. Is this a misconfiguration on my
part or am I supposed to run them as Linux Cron Jobs?

They should be working, however you will probably need to prefix mutil with "./" if you haven't already, e.g.:

./mutil /mnt/bbs/mystic/import.ini

...if you haven't got your Mystic root directory in the daemon user's PATH, as Mystic launches all binaries from the Mystic root directory.

Best regards
Zip

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

Mail Import / Export and Events don't appear to trigger automatically
when using the daemon under linux. Is this a misconfiguration on my
part or am I supposed to run them as Linux Cron Jobs?

In addition to Zip's feedback, once you update these event type jobs, you'll need to stop and restart the mis daemon; it doesn't live reload these config changes.

--- Mystic BBS v1.12 A46 2020/04/13 (Linux/64)
* Origin: monterey bbs (21:1/168)

On 09 May 2020, Zip said the following...

Hello Nazferiti!

On 08 May 2020, Nazferiti said the following...

Mail Import / Export and Events don't appear to trigger automatically when using the daemon under linux. Is this a misconfiguration on my part or am I supposed to run them as Linux Cron Jobs?

They should be working, however you will probably need to prefix mutil with "./" if you haven't already, e.g.:

./mutil /mnt/bbs/mystic/import.ini

...if you haven't got your Mystic root directory in the daemon user's PATH, as Mystic launches all binaries from the Mystic root directory.

This is probably my problem then, I installed my linux, copied over all my config and user files from my Windows 32 version. Currently I have
everything set as a cron and mail is flowing, but I think it would be better
to have mail crash rather than just force a poll ever half hour.

- Mike

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Arcadia BBS | Connecticut USA | bbs.arcadiabbs.com (21:3/107)

They should be working, however you will probably need to prefix mutil with "./" if you haven't already, e.g.:

./mutil /mnt/bbs/mystic/import.ini

You guys are awesome, I made those changes and it's working perfectly now! Been a busy day, got almost everything working in Linux now. Even got MRC
up and running!

- Mike

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Arcadia BBS | Connecticut USA | bbs.arcadiabbs.com (21:3/107)

Hello Nazferiti!

On 09 May 2020, Nazferiti said the following...

my config and user files from my Windows 32 version. Currently I have everything set as a cron and mail is flowing, but I think it would be better to have mail crash rather than just force a poll ever half hour.

Actually you can have both -- first an Interval event polling e.g. every hour:

▄▄ █ ───█ Active │ Yes █────█▓gj!
██▄▄█ No █ Description │ CUSTOM: Poll echomail/netmail Sun │ No █ ░█▄▄
░████ No █ Event Type │ Interval Mon │ No █----░██▒■ ▀ ▓███ No █ Exec Hour │ 1 Tue │ No █ ░████ ▓ ▒▓▓█ No █ Exec Min │ 0 Wed │ No █ ░▓░
▓ █░░█ Yes█ Shell │ timeout -k 600 --preserve-stat Thu │ No █WTFS ░█░ ▓ ░░▓███ Yes█ Semaphore │ Fri │ No █ ░ ▄▄█ ▄▄■ ▀█ Yes█ Kill After │ Sat │ No █ ░ █░░
█ Yes█ Warning │ 0 █ ░ ▀▄

Complete Shell command line: timeout -k 600 --preserve-status -v 600 ./mis
poll forced

...and then also a semaphore event watching for indications of outgoing mail:

█ ───█ Active │ Yes █────█▓gj!
██▄▄█ No █ Description │ CUSTOM: Send outbound echomail Sun │ No █ ░█▄▄
░████ No █ Event Type │ Semaphore Mon │ No █
▀ ▓███ No █ Exec Hour │ 0 Tue │ No █----
▓ ▒▓▓█ No █ Exec Min │ 0 Wed │ No █ ░▓░
▀ █░░█ No █ Shell │ ./mutil /mnt/bbs/mystic/export Thu │ No █ ░█░ ░░▓███ Yes█ Semaphore │ echomail.out|netmail.out Fri │ No █WTFS ░
▄▄■ ▀█ Yes█ Kill After │ netmail.out Sat │ No █ ░
█ Yes█ Warning │ 0 █ ░ ▀▄

Complete Description line: CUSTOM: Send outbound echomail/netmail
Complete Shell command line: ./mutil /mnt/bbs/mystic/export.ini|timeout -k 600 --preserve-status -v 600 ./mis poll send

(At least in the past, mutil ExportEchoMail didn't remove netmail.out after sending, so I ask the event to remove it if left over.)

...and, finally, another semaphore event watching for incoming mail to toss:

▄▄ █ ───█ Active │ Yes █────█▓gj!
██▄▄█ No █ Description │ CUSTOM: Toss incoming echomail Sun │ No █ ░█▄▄
░████ No █ Event Type │ Semaphore Mon │ No █ ░██▒■ ▀ ▓███ No █ Exec Hour │ 0 Tue │ No █ ░████ ▓ ▒▓▓█ No █ Exec Min │ 0 Wed │ No █ ░▓░ ▓▀ █░░█ No █ Shell │ ./mutil /mnt/bbs/mystic/import Thu │ No █---- ░█░ ▓ ░░▓███ No █ Semaphore │ echomail.in Fri │ No █ ░ ▄▄█ ▄▄■ ▀█ No █ Kill After │ Sat │ No █ ░ █░░
█ Yes█ Warning │ 0 █WTFS ░ ▀▄

Complete Description line: CUSTOM: Toss incoming echomail/netmail
Complete Shell command line: ./mutil /mnt/bbs/mystic/import.ini

I've had some problems with the pre-alpha A46 'mis poll' consuming 100% CPU
due to some timer-related stuff (clock not increasing monotonically?), so I added the 'timeout' safety net to ensure it won't get stuck for ever
(requiring a MIS service restart).

N.B.: 'mis poll' is not available in A45, it was introduced in the pre-alpha A46s. The equivalent of 'mis poll' for A45 would be 'fidopoll'.

Best regards
Zip

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

Hello Nazferiti!

On 09 May 2020, Nazferiti said the following...

You guys are awesome, I made those changes and it's working perfectly
now! Been a busy day, got almost everything working in Linux now. Even

Glad to hear that! :D
Well done!

Best regards
Zip

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