It's interesting you mentioned /tmp. That's what started this entire exercise. We migrated our /tmp filesystem from a ZFS to TFS and ran into a problem with our scheduling product. Turned out that it's documented that the product doesn't support TFS event triggering. So if batch job put a file in /tmp when it was a ZFS the scheduling product would see it and kick off a job.
Once we migrated /tmp to a TFS, the triggering didn't occur. Trying to simulate that behavior with a ZFS file system. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com ------- Original Message ------- On Monday, March 27th, 2023 at 1:56 PM, Rick Troth <tro...@gmail.com> wrote: > I'm not sure that's possible. > In any case, I don't know specifically how to do it. > > Best practice on Unix is for /tmp to be set as 'chmod 1777'. That way, > anyone can write to /tmp but they can then only delete or rename or move > files which they own. But if you then created a sub-directory like > /tmp/mything it would not necessarily inherit the same permissions. > > Now ... you could run a cron job to 'chmod a+rw /foo/bar'. That's > inelegant, but would give the desired effect (if you can tolerate the > race condition between cron runs). > > All of this is about 'chmod' and you mention 'setfacl'. > I've used 'setfacl' to great effect, but not used the "default" options. > So this is the limit of my knowledge on the subject, but I didn't see > anyone else reply. > > -- R; <>< > > > > > On 3/27/23 08:11, Mark Jacobs wrote: > > > I want a directory that anyone can write to/read from and for any files or > > directories created under it also to be world readable/writable by default. > > > > Mark Jacobs > > > > Sent from ProtonMail, Swiss-based encrypted email. > > > > GPG Public Key > > -https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com > > > > ------- Original Message ------- > > On Monday, March 27th, 2023 at 8:05 AM, Rick trothtro...@gmail.com wrote: > > > > > I started a longer reply, but got stuck in the weeds. > > > > > > Can you describe what you're trying to do? > > > > > > -- R; <>< > > > > > > On 3/27/23 07:10, Mark Jacobs wrote: > > > > > > > I’ve never been able to get the setfacl command to do what I’m trying > > > > to do. Any assistance would be appreciated. I’m trying to set the > > > > default ACL for any new files or directories created in /foo/bar to be > > > > world readable/writable, in short I’m looking for the permissions set > > > > to 666 for those newly created files/directories. > > > > > > > > Mark Jacobs > > > > > > > > Sent from ProtonMail, Swiss-based encrypted email. > > > > > > > > GPG Public Key > > > > -https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com > > > > > > > > ---------------------------------------------------------------------- > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > > send email tolists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > > > ---------------------------------------------------------------------- > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email tolists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > ---------------------------------------------------------------------- > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email tolists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
