On Tue, Nov 05, 2019 at 04:43:59AM +0100, Jonathan Drews wrote: > To: [email protected] > Subject: Small error in chflags man page > From: Jonathan > Cc: cleetus > Reply-To: [email protected]>Synopsis: chflags man page has an > error > >Category: Documentation > >Environment: > System : OpenBSD 6.6 > Details : OpenBSD 6.6 (GENERIC.MP) #1: Sun Oct 27 16:19:23 MDT 2019 > [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP > Architecture: OpenBSD.amd64 > Machine : amd64 > >Description: > The man page for chflags says to prepend "no" to one of the > flags. To unset the nodump flag you would then do: > $chlags nonodump file.txt > However this does not work. > >How-To-Repeat: > leo$ ls -lohd mp3/ > drwxr-xr-x 15 cleetus cleetus uchg,nodump 512B May 6 14:33 mp3/ > leo$ chflags -R nonodump mp3/ > chflags: invalid flag: nonodump > leo$ chflags -R dump mp3/ > leo$ ls -lohd mp3/ > drwxr-xr-x 15 cleetus cleetus uchg 512B May 6 14:33 mp3/ > leo$>Fix: > The man page should say: Putting the letters no before a flag name causes > the flag to > be turned off except in the case of the nodump flag. To turn > off nodump, use dump. Do not use nonodump. > EXAMPLE: > chflags dump somefile.txt
morning. i think part of this is just learning curve. if you think about it, there's enough info there to work it out. the question would be more whether specifying "dump" actually does anything other than achieve what already happens if you don;t specify "nodump". other than that, i think there's enough there to work it out. jmc
