Manual page for mq_getfd_np(2)

[unitrunker_gmail.com]

Summary

mq_getfd_np was made available in FreeBSD 11 with no documentation.

Under the hood - this function dereferences the mqd_t as a pointer to an int.

It's a simple function but needs guidance on what is safe usage for the returned file descriptor.

Please review - particularly the "Notes" section.

Test Plan

Ran the following to confirm behavior.

• fork followed by fstat in both parent and child process (confirmed mqd_t and fd remain valid).
• close before mq_close (not a good practice - see "Notes")
• mq_close before close (also not a good practice - see "Notes")

Test program attached to bug 273230.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273230

[concussious.bugzilla_runbox.com]

lib/libsys/mq_getfd_np.2

2

Tried to put this at the very top but it didn't work out.

https://man.freebsd.org/cgi/man.cgi?query=style&apropos=0&sektion=0&manpath=FreeBSD+

43

This doesn't need to be quoted

57

Why a blank line? .Pp?

[pauamma_gundo.com]

lib/libsys/mq_getfd_np.2

53

63

65

74

86

87

92–94

116

[unitrunker_gmail.com]

• feedback from concussious
• feedback from pauamma_gundo
• trimmed some trailing blanks

[pauamma_gundo.com]

lib/libsys/mq_getfd_np.2

67

89

[pauamma_gundo.com]

I'd like someone who knows about this system call to review this as well.

[unitrunker_gmail.com]

fix typos caught by pauamma_gundo

[kib]

lib/libsys/mq_getfd_np.2

38

Was it? The function is non-standard, which part of the text was copied?

55

67

Why this property needs a special mention?

79

New sentence new line. I am not sure that these 'do not call close' are useful. It is better to formulate that the fd is owned by the mq descriptor.

99

otherwise part is weird and most likely should be just omitted.

103

again, 'but may ...' part should be omitted.

114

I do not see a point of listing all mq* functions. Only list functions that are referenced in the body of the man page, and perhaps mqueuefs(5)