Email List: Xaustin-review-lX
[All Lists]

Defect in XCU fuser

To: yyyyyyyyyyyyyyy@xxxxxxxxxxxxx
Subject: Defect in XCU fuser
From: yyyyy@xxxxxxxxxx
Date: Fri, 3 Mar 2006 22:17:09 GMT
        Defect report from : Mark Brown , IBM

(Please direct followup comments direct to yyyyyyyyyyyyyy@xxxxxxxxxxxxx)

@ page 472 line 18282 section fuser editorial {AG-AI-2006-02-16}

Problem:

Edition of Specification (Year): 2004

Defect code :  3. Clarification required

Ref: Austin Group action AI-2006-02-16 arising from the Plenary of February 2006

The example accompanying the fuser description is not sufficient to make clear 
how the various options work when operating on mount points and block devices.

Action:

Add the following text after line 18282:

fuser -c <mount point>

writes to standard output the process IDs of processes that are using any file 
in the filesystem which is mounted on <mount point> and writes to standard 
error an indication of how those processes are using the files.

fuser <mount point>

writes to standard output the process IDs of processes that are using the file 
which is named by <mount point> and writes to standard error an indication of 
how those processes are using the file.

fuser <block device>

writes to standard output the process IDs of processes that are using any file 
which is on the device named by <block device> and writes to standard error an 
indication of how those processes are using the file.

fuser -f <block device>

writes to standard output the process IDs of processes that are using the file 
<block device> itself and writes to standard error an indication of how those 
processes are using the file.

<Prev in Thread] Current Thread [Next in Thread>
  • Defect in XCU fuser, bmark <=