herringm at denison
Jul 19, 2011, 8:17 AM
Post #5 of 7
Re: Checkin & Publish workflow not updating file timestamps
[In reply to]
Try seeing if there is any clock skew between your Bricolage server and
the end-point destination server.
On Jul 16, 2011, at 11:13 AM, Matt Adams wrote:
>>> Sorry - maybe I messed up the details. Let's see if I can get this straight. This is what's happening:
>>> 1) Neither "Checkin& Publish" nor "Publish Now" will generate a file with a new timestamp. A file with the new content makes its way to the server but the existing timestamp is used.
>>> 2) Republishing generates files with new timestamps. This causes changes to content to be reflected immediately.
>>> Essentially what we want is for either of the #1 use cases to generate files with new timestamps just like republishing.
>> They should exhibit exactly the same behavior. Very weird.
>>> We're using the built-in SFTP mover with bric_queued. FTP_UNLINK_BEFORE_MOVE is turned on.
>> Here's the code:
>> # Now, put the file on the server.
>> my $dest_file = $fs->cat_file(
>> $doc_root, unescape_uri substr $res->get_uri, 1
>> my $temp_dest = "$dest_file.tmp";
>> $sftp->unlink($temp_dest) if FTP_UNLINK_BEFORE_MOVE;
>> $ssh2->scp_put($src, $temp_dest) or throw_gen(
>> error => "Error putting file '$dest_file' on '$hn'",
>> payload => join ' ', $ssh2->error
>> $sftp->unlink($dest_file) if FTP_UNLINK_BEFORE_MOVE;
>> $sftp->rename($temp_dest, $dest_file) or throw_gen(
>> error => "Error renaming '$temp_dest' to '$dest_file' on '$hn'",
>> payload => join ' ', $sftp->error
>> It does nothing to adjust mtimes or anything. What happens if you turn off FTP_UNLINK_BEFORE_MOVE, just for the hell of it?
Information Technology Services
herringm [at] denison