I'm trying to serve NFS. I keep getting 'mountd No default domain set' whenever I try to mount the filesystem from the client. What is/how to fix this?

I can mount Solaris 9's share on Linux, so this is likely something on OmniOS.

Oh I forgot "@" in zfs sharenfs='rw=@192.168.20.0/24 pool/...'. Working now.

I would like to reach the maintainer of Nagios package on OmniOS to tell him that we should use mailx command instead of mail command with actions « notify-host-by-email » and « notify-service-by-email » in file /etc/opt/ooce/nagios/objects/commands.cfg because the « -s » flag that is used there has no effect in the OmniOS version of

mail command (contrarily to the mail command of Linux distributions) and, thus, prevent email notifications from having a subject by default. Just using « mailx » instead of « mail » (while using the same arguments) correct the problem.

Yes, invoking mailx would be much better (and posixly more correct). FWIW: many linux "mail"s don't support -s, either; and often enough, there's no "mail" at all.

On RHEL 8, "-s" works with "mail" command but you may be right about other distributions

In the good old days, /usr/bin/mail was very stupid. If you wanted smart you used Mail or mailx (depending on who you were paying attention to).

It doesn't surprise me that leeenux decided to ditch the original /usr/bin/mail at some point, much like /bin/sh is really /bin/bash in a trenchcoat.

Thanks for your input neitzel and nomad :)

The Manifest file for the nagios pkg says: "set name=publisher value=sa⊙oo", so maybe that's the answer. The manifests also lists the file /opt/ooce/share/doc/release-notes/ooce_application_nagios -- perhaps that has some contact info, too.

Depends on the distro. /bin/mail, /bin/Mail, and /usr/bin/mail are symlinks to /usr/bin/mailx on Slackware.

I've just checked and there is no contact info in /opt/ooce/share/doc/release-notes/ooce_application_nagios or /opt/ooce/nagios/share/README.md

is sa⊙oo the email address to use for all packages?

I wouldn't be surprised -- I really don't know. I'll boot an omnios box myself in a few minutes and have a look at various pkg(1) outputs to see if there's anything better to find.

(y)

Nope, wasn't able to find anything better.

question: I'm trying up upgrade a host, and I'm getting a conflict between python 3.9 and 3.12. Any advice on fixing it?

According to github.com/citrus-it/omnios-extra/blob/master/doc/packages.md nagios is maintained by the omnios team, although I remember it being contributed. Anybody can do a pull request or raise an issue against that repository though and this sounds like something that needs addressing.