Thread: signify with -C
View Single Post
  #4   (View Single Post)  
Old 14th September 2021
IdOp's Avatar
IdOp IdOp is offline
Too dumb for a smartphone
 
Join Date: May 2008
Location: twisting on the daemon's fork(2)
Posts: 1,027
Default

In that example, I'm thinking that

$ sha256 * > SHA256

will create a checklist file SHA256 containing entries for files a, b and c, but not for itself since it doesn't exist when the * is interpreted. The next command

$ sha256 -C SHA256 *

then tests each file referenced by * against the checklist file entries. At this point the * does pick up SHA256 --- because it now exists --- and this leads to an error as indicated in sha256(1) about the -C option:

Quote:
Any specified file that is not listed in the checklist will generate an error.
Reply With Quote