I'm curious how Mystic handles permissions when shelling for events.

I have the MIS daemon set to run as a service. As I understand it, root priviledges are used to bind to port 23 (anything under port 1024 requires root) and then proceeds to use the "mystic" user (which I have setup).

I noticed the events aren't firing, rather they come back with
"Process result 127"

Here is an excerpt from my server_events.log

-------------------------------------------------------------------------
Oct 12 08:57:48 Executing "Poll fsxNet Hub"
Oct 12 08:57:48 Command line: fidopoll forced
Oct 12 08:57:48 Process result 127
Oct 12 08:57:48 Command line: mutil mailin.ini
Oct 12 08:57:48 Process result 127
Oct 12 09:06:49 Executing "Send outbound echomail"
Oct 12 09:06:49 Detected semaphore: /mystic/semaphore/netmail.out
Oct 12 09:06:49 Command line: mutil mailout.ini
Oct 12 09:06:49 Process result 127
Oct 12 09:06:49 Command line: fidopoll send
Oct 12 09:06:49 Process result 127
Oct 12 09:06:49 Command line: mutil mailin.ini
Oct 12 09:06:49 Process result 127 -------------------------------------------------------------------------

But when I check the message bases, no new messages have arrived.
When I run ./mutil mailin.ini manually, the messages are processed.

Maybe I need to preface the shell command in configuration with ./
in case the current directory is not assumed when shelling to events.

Thanks!
-Ian

--- Mystic BBS v1.12 A34 (Linux/32)
* Origin: The Vista BBS - Vallejo, CA USA (21:1/142)

Maybe I need to preface the shell command in configuration with ./
in case the current directory is not assumed when shelling to events.

Never mind. After following my own advice, I put the absolute path in the shell command and I am now seeing "Process result 0" so I will now monitor to make sure messages are being tossed on a regular basis.

--- Mystic BBS v1.12 A34 (Linux/32)
* Origin: The Vista BBS - Vallejo, CA USA (21:1/142)

On 10/12/17, it pondered and said...

I have the MIS daemon set to run as a service. As I understand it, root priviledges are used to bind to port 23 (anything under port 1024
requires root) and then proceeds to use the "mystic" user (which I have setup).

Yes Mystic only uses root for a short space of time then drops back to a regular user :)

I noticed the events aren't firing, rather they come back with
"Process result 127"

Yep something is amiss..

Oct 12 08:57:48 Executing "Poll fsxNet Hub"
Oct 12 08:57:48 Command line: fidopoll forced
Oct 12 08:57:48 Process result 127
Oct 12 08:57:48 Command line: mutil mailin.ini
Oct 12 08:57:48 Process result 127

But when I check the message bases, no new messages have arrived.
When I run ./mutil mailin.ini manually, the messages are processed.

Maybe I need to preface the shell command in configuration with ./
in case the current directory is not assumed when shelling to events.

Correct, preface each command in the shell line with ./

so ./mutil mailin.ini|./fidopoll send

for example :)

Best, Paul

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

On 10/12/17, it pondered and said...

Never mind. After following my own advice, I put the absolute path in
the shell command and I am now seeing "Process result 0" so I will now monitor to make sure messages are being tossed on a regular basis.

Yay! :)

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

Hello it,

But when I check the message bases, no new messages have arrived.
When I run ./mutil mailin.ini manually, the messages are processed.
Maybe I need to preface the shell command in configuration with ./
in case the current directory is not assumed when shelling to events.

Two things to try come to mind. One is to put the complete path to the executable in the commandline as in /home/<user>/mystic/<executable>.

Or preface the executable with a "./" as in ./mutil <config file>

Jeff

--- BBBS/Li6 v4.10 Toy-3
* Origin: FsxNet: The Ouija Board - bbs.ouijabrd.net (21:1/128)

On 10/12/17, it said the following...

Maybe I need to preface the shell command in configuration with ./
in case the current directory is not assumed when shelling to events.

Yes, you need the ./fidopoll 21:1/100 for example to reach FSXNet old main
hub (there are two others now). I find with Linux full path is the best way
as then it works under Events in mystic & crontab. You will find you want to >/dev/null in crontab or you'll get email for each event (if any output).
I use Ubuntu (32&64 bit) & Raspbian (32 bit), they all work pretty much the same and better with mis2 doing telnet (binkp works either way under mis or mis2 fine). SSH & rlogin are only for mis2 and the rest (ftp, pop3, smtp,
nntp) are on mis at present.

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Workpoint (21:1/145.3)

Never mind. After following my own advice, I put the absolute path in
the shell command and I am now seeing "Process result 0" so I will now monitor to make sure messages are being tossed on a regular basis.

Yes, I had the same problem. You need to put in the full path in order for
the events to run under linux.

Kate.

---------------
Flower BBS
telnet: bbs.homeip.net
fsxNet: 21:2/123

--- Mystic BBS v1.12 A34 (Linux/64)
* Origin: Flower BBS (21:2/123)

On 10/12/17, it said the following...

Maybe I need to preface the shell command in configuration with ./
in case the current directory is not assumed when shelling to events.

Never mind. After following my own advice, I put the absolute path in
the shell command and I am now seeing "Process result 0" so I will now monitor to make sure messages are being tossed on a regular basis.

I don't have the absolute path in mine but I do have ./ in front of all the commands and it runs properly.

Immortal

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

I have the MIS daemon set to run as a service. As I understand it, root priviledges are used to bind to port 23 (anything under port 1024
requires root) and then proceeds to use the "mystic" user (which I have setup).

It uses whatever user owns the mis file. If that is owned by root, it'll
stay root (for example).

I noticed the events aren't firing, rather they come back with
"Process result 127"

Value 127 is returned by /bin/sh when the given command is not found within your PATH system variable and it is not a built-in shell command. In other words, the system doesn't understand your command, because it doesn't know where to find the binary you're trying to call.

In other words, you probably need to add the path in.

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)