MFAKTC worktodo.txt permissions keep changing back

[bgbeuning]

I never run mkaftc as root and it works fine.
When mfaktc removes a task in worktodo.txt,
it creates a new file to replace it. The new file
is owned by the user running the process, or root.

[Rodrigo]

Yes, I too understand this now. I'd always thought that worktodo.txt was "edited" (deleting the completed exponent) and then saved, but it does look like a new file gets created each time.

Thanks very much.

[Mark Rose]

What is the output of `ls -l mfaktc-0.21`? Specifically, maybe you've set a sticky bit on the mfaktc.exe executable.

[Rodrigo]

I'm still new to this, so I'm not sure what you're asking for, exactly.

If you mean the ls -l result for the executable, it's

-rwxr-xr-x 1 rodrigo rodrigo

If OTOH you mean the ls -l output for all the files in the MFAKTC-0.21 directory, I'll move over to that computer (I'm typing this on a different PC) and copy-paste it over to a new post in this thread. (Lower chance of introducing errors than if I were to retype the output.)

[chalsall]

Originally Posted by Rodrigo

I'd always thought that worktodo.txt was "edited" (deleting the completed exponent) and then saved, but it does look like a new file gets created each time.

A standard "trick" of programmers it to create a new file, and then move it over the old file. This has the advantage that if any other program is watching the old file it doesn't disappear until every program which has a lock on it stops watching.

This probably explains why the permissions are changing on that file.

[Rodrigo]

Just want to thank everyone who offered an idea, suggestion, or insight, no matter the angle it came in from. This was a very educational experience.

BTW the whole setup has been working like a well-oiled machine.