Update of sr #110453 (project administration):
Status: None => In Progress
Assigned to: None => rwp
_______________________________________________________
Follow-up Comment #2:
And then, pretty much while I was still looking at things, it updated. Now
"cvs -qn up" shows that the pages are all up to date. And the timestamps on
those pages in the web server side of things are from just a few minutes ago.
For example this one.
-rw-rw-r-- 1 wwwcvs wwwcvs 3.9K Mar 1 02:46 Use-Scenarios.html
Therefore I think it successfully updated. But what changed? I don't know.
Mon Mar 1 02:46:01 EST 2021
ctlseqs: Beginning checkout (type non-gnu)
cvs2 checkout: Updating ctlseqs
cvs2 checkout: Updating ctlseqs/install
cvs2 checkout: Updating ctlseqs/manual
U ctlseqs/manual/ctlseqs.dvi.gz
U ctlseqs/manual/ctlseqs.html
U ctlseqs/manual/ctlseqs.html.gz
U ctlseqs/manual/ctlseqs.html_node.tar.gz
U ctlseqs/manual/ctlseqs.info.tar.gz
U ctlseqs/manual/ctlseqs.pdf
U ctlseqs/manual/ctlseqs.texi.tar.gz
U ctlseqs/manual/ctlseqs.txt
U ctlseqs/manual/ctlseqs.txt.gz
U ctlseqs/manual/index.html
cvs2 checkout: Updating ctlseqs/manual/html_node
U ctlseqs/manual/html_node/API-Reference.html
U ctlseqs/manual/html_node/Contributing.html
U ctlseqs/manual/html_node/Control-Sequence-Matching.html
U ctlseqs/manual/html_node/Control-Sequence-Reading.html
U ctlseqs/manual/html_node/Example-Programs.html
U ctlseqs/manual/html_node/GNU-Free-Documentation-License.html
U ctlseqs/manual/html_node/Helper-Macros.html
U ctlseqs/manual/html_node/Matcher-Configuration.html
U ctlseqs/manual/html_node/Matching-String.html
U ctlseqs/manual/html_node/Overview.html
U ctlseqs/manual/html_node/Patterns.html
U ctlseqs/manual/html_node/Tips.html
U ctlseqs/manual/html_node/Use-Scenarios.html
U ctlseqs/manual/html_node/index.html
ctlseqs: CVS checkout completed (type non-gnu)
While digging around I have figured out that the new.py program doesn't ever
actually do the update. It touches a file in a directory with the project
name. Then there is a cronjob that runs every two minutes that scans the
directory and then takes action. Among other things this allows the web
server to run as one user id and the update to run as a different user id for
the update. That's a nice security layer.
That the cron job does run every two minutes means that it won't happen
immediately, immediately. But it will happen pretty soon. Probably soon
enough.
It also means that it might be updating several projects all at once. It will
work through the list in alphabetical order. So project B could be delayed a
little if it is behind project A and both are to be updated and if A is very
big. But that does not seem to be the case here either.
Right now my best working theory is either that the loginfo hook script is not
right in some way. Therefore I wasn't not triggered when you updated. Or
that you updated during the storage array breakage time his morning. Which
also prevented the update. I did manually trigger a curl hit to new.py and
that would have queued an update. I did immediately look and it wasn't
updated yet. But at the time I did not know about the 2 minute delay and did
not wait for it.
It's late here now. I will look at it in more detail tomorrow and try some
tests then to verify that it is either working or not working.
_______________________________________________________
Reply to this item at:
<https://savannah.nongnu.org/support/?110453>
_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/
