On 11/7/18 5:58 PM, Bernhard Voelker wrote:
> tag 33303 notabug
> close 33303
> thanks
>
> On 11/7/18 5:07 PM, L A Walsh wrote:
>> Was looking to see when the underlying filesystem
>> changed in a path.
>>
>> I used:
>>> stat -f -c%f /
>> 821
>> stat -f -c%i /var
>> 822
sorry, I
tag 33303 notabug
close 33303
thanks
On 11/7/18 5:07 PM, L A Walsh wrote:
> Was looking to see when the underlying filesystem
> changed in a path.
>
> I used:
>> stat -f -c%f /
> 821
> stat -f -c%i /var
> 822
>
> There are way too many zeros, not to mention being left justfied
>
Was looking to see when the underlying filesystem
changed in a path.
I used:
stat -f -c%f /
821
stat -f -c%i /var
822
There are way too many zeros, not to mention being left justfied
with zeros.
What I might expect to see is more like this:
821
or
822
mountpoint -d shows the
On Wednesday, November 7, 2018 12:33:45 AM CET Bernhard Voelker wrote:
> On 11/6/18 7:35 PM, Paul Eggert wrote:
> > Thanks, I installed that and am closing the bug report.
>
> That was a real bug, i.e., not only a resource leak, wasn't it?
>
> If the calling user has -r+w permissions on the file,
