Thanks Jacob, but I still don't quite understand :-)
for example, I have a file a with mode set to 7755
# ls -l a
-rwsr-sr-t. 1 root root 2 Mar 15 23:46 a
# stat a
  File: 'a'
  Size: 2               Blocks: 2          IO Block: 4194304 regular file
Device: 34h/52d Inode: 48128       Links: 1
Access: (7755/-rwsr-sr-t)  Uid: (    0/    root)   Gid: (    0/    root)
Context: unconfined_u:object_r:unlabeled_t:s0
Access: 2022-03-15 23:42:19.390236000 +0800
Modify: 2022-03-15 23:48:19.760428000 +0800
Change: 2022-03-15 23:48:19.760350205 +0800
 Birth: -

but in the event, the permission is "200107755", so it seems the first 7 is
setuid/setgid/sticky bit(all set), how about "20010"?

On Tue, Mar 15, 2022 at 10:12 PM Jacob M Tick <[email protected]> wrote:

> Hi,
>
>
>
> Here is some information on those bits. It's essentially special file
> bits... As such:
> https://www.gnu.org/software/coreutils/manual/html_node/Mode-Structure.html
>
>
>
> We have the permission bits + other bits for setuid setgid and sticky bits.
>
>
>
> Regards,
>
>
>
> *Jake Tick*
>
> Development Manager
>
> Spectrum Scale - Scalable Data Interfaces
>
> IBM Systems Group
>
>
>
> Email: [email protected]
>
>
>
> IBM
>
>
>
> *From: *gpfsug-discuss <[email protected]> on behalf of
> shao feng <[email protected]>
> *Reply-To: *gpfsug main discussion list <[email protected]>
> *Date: *Sunday, March 13, 2022 at 6:10 PM
> *To: *"[email protected]" <[email protected]>
> *Subject: *[EXTERNAL] [gpfsug-discuss] permissions in clustered watch
> folder events
>
>
>
> Hello all,
>
>
>
> I am prototyping a solution which collects all the file information into a
> database by utilizing the clustered watch folder feature. I found the
> permissions field in the JSON from kafka topic is something
> like "permissions": "200100600". It seems the "600" part is the same as
> UNIX file permission, but what does the "200100" part stand for?
>
>
>
> Thank you!
>
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at gpfsug.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org

Reply via email to