Read-only error?

[Xyzzy]

We were testing some things today and ran the nc1 stage on some work. At the end of the nc1 stage, msieve threw an error about msieve.dat.gz being read-only. However, when we ran it so that msieve.dat.gz could be written to, the file was not changed. (The nc1 job finished with no error.)

So why does msieve want to write to msieve.dat.gz if it never does?

$ md5sum 144/msieve.dat.gz 
06da203c1006e8d7416db358a9262bc5  144/msieve.dat.gz
$ md5sum backup/msieve.dat.gz 
06da203c1006e8d7416db358a9262bc5  backup/msieve.dat.gz

[chalsall]

Originally Posted by Xyzzy

We were testing some things today and ran the nc1 stage on some work. At the end of the nc1 stage, msieve threw an error about msieve.dat.gz being read-only. However, when we ran it so that msieve.dat.gz could be written to, the file was not changed. (The nc1 job finished with no error.)

This is probably SELinux.

Originally Posted by Xyzzy

So why does msieve want to write to msieve.dat.gz if it never does?

Good question.

[frmky]

msieve opens the dat file for both reading and writing so that it can add free relations if they aren't already there. If you have already run this dat file once with msieve, then nothing new was added.