ctime check for restart file

[Nate Mueller]

Just wondering what the reason was for checking both the mtime and
ctime on the restart file. We've been trying to track down some
mysterious restarts in production that ended up being triggered by an
errant chown. The docs all talk about touching the file so when we
didn't see the mtime changing we thought it was some crazy bug.

In our case we shouldn't have been doing the chown anyway but I was
wondering if anyone has run into this before.

[Hongli Lai]

It's meant as an extra check just in case. But chown shouldn't change the ctime should it?

Sent from my Android phone.

Op 15 feb. 2012 20:40 schreef "Nate Mueller" <na...@nearbuysystems.com> het volgende:

--
You received this message because you are subscribed to the Google Groups "Phusion Passenger Discussions" group.
To post to this group, send email to phusion-...@googlegroups.com.
To unsubscribe from this group, send email to phusion-passen...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/phusion-passenger?hl=en.

[Nate Mueller]

It's meant as an extra check just in case. But chown shouldn't change the ctime should it?

ctime is the last change time on the inode so it will increase any time you change ownership or permissions, as well as any time you change the contents.  mtime is only updated when the file contents change.

--Nate