A NOTE has been added to this issue. ====================================================================== https://austingroupbugs.net/view.php?id=1746 ====================================================================== Reported By: geoffclare Assigned To: ====================================================================== Project: 1003.1(2016/18)/Issue7+TC2 Issue ID: 1746 Category: Shell and Utilities Type: Clarification Requested Severity: Objection Priority: normal Status: New Name: Geoff Clare Organization: The Open Group User Reference: Section: fuser Page Number: 2817 Line Number: 92698 Interp Status: --- Final Accepted Text: ====================================================================== Date Submitted: 2023-06-13 15:58 UTC Last Modified: 2023-06-13 20:20 UTC ====================================================================== Summary: fuser output format clarification ======================================================================
---------------------------------------------------------------------- (0006330) kre (reporter) - 2023-06-13 20:20 https://austingroupbugs.net/view.php?id=1746#c6330 ---------------------------------------------------------------------- Why the change from %d to %1d ? The default for %d is %1d according to XBD 5. Putting the '1' there just causes readers to wonder why? Unless explicitly given as %0d, %d (and all the related ones) always outputs at least one character. You also omitted the "for each process using that file" from the final sentence. But the STDOUT section still says: The fuser utility shall write the process ID for each process using each file given So there can clearly be more than one pid printed for one file, and hence possibly more than one user. It isn't clear if the multiple user names/uids should each appear in their own set of parentheses, or if one set should surround all of them, and in the latter case if any separation is supplied. It also isn't clear, as the -u option mentions nothing about what happens with multiple processes whether each user name (or uid) is written just once, or once for each pid. There is nothing, in the current, or proposed new, text which says there should be any correlation between the order in which the pids are printed, and the order the user names (or uids) are printed, nor for that matter, the order in which any 'c' or 'r' characters are written, nor whether there is intended to be any way to relate one of those to a pid, particularly if an implementation chooses not to output other characters for other uses of the file, nor what should be done if the same file is open by the same process for several different uses (we may have the root directoru as our current directory (both 'r' and 'c') and also have it open for reading to obtain a directory listing (like "cd /; ls' when the "fuser /" command is given, and that ls process is located as one user of that directory). I can't test any of this, NetBSD has no fuser command - and given the description of it, I'm not surprised, it looks foul to use (we do have a utility which provides similar information in a totally different format). I'd be in favour of obsoleting this trash... If not, I think its description needs a complete rewrite, something I cannot assist with, as I have no idea at all what it really does (I can see what it is intended for, just not the details of how it really operates). Issue History Date Modified Username Field Change ====================================================================== 2023-06-13 15:58 geoffclare New Issue 2023-06-13 15:58 geoffclare Name => Geoff Clare 2023-06-13 15:58 geoffclare Organization => The Open Group 2023-06-13 15:58 geoffclare Section => fuser 2023-06-13 15:58 geoffclare Page Number => 2817 2023-06-13 15:58 geoffclare Line Number => 92698 2023-06-13 15:58 geoffclare Interp Status => --- 2023-06-13 20:20 kre Note Added: 0006330 ======================================================================
