Checkout/update timestamp

Comments (6)

1. 

   Eric Seidel

   • changed status to open
   • removed comment

   GetComponents already logs errors with a timestamp, and the error message that was produced. The logs are placed in $HOME/.crl/crl.log. I do like your idea of adding a short log message when the tree is successfully updated though.

   • 2010-11-02T10:31:52+00:00
2. 

   Ian Hinder reporter

   • removed comment

   What is "CRL"? I understood it as "certificate revocation list". Is CRL another name for GetComponents? Why is the log stored in the home directory, rather than in the Cactus tree that is being checked out? Can the information about the logging be added to the documentation? Before I raised the ticket, I looked in the documentation to find out if there was a log file, and couldn't find anything.

   • 2010-11-02T11:05:55+00:00
3. 

   Eric Seidel

   • removed comment

   CRL is the Component Retrieval Language, the language we designed for writing the component lists. I thought it would make more sense to store a log of all GetComponents stuff in a central location, as opposed to having separate logs for each checkout. Also, we had talked about storing the component lists in $HOME/.crl as well, so you could just run GetComponents inside your checkout without specifying a component list, but I never had time to implement that feature.

   I didn't realize that the log is not mentioned anywhere in the documentation. I'll fix that, I want to clean it up some too.

   • 2010-11-02T14:42:57+00:00
4. 

   Eric Seidel

   • removed comment

   This issue has been addressed in the Git repository. The svn version will be patched following the ET_2010_11 release.

   • 2010-11-10T15:30:13+00:00
5. 

   Eric Seidel

   • changed status to resolved
   • removed comment

   issue resolved in revision 706 of the svn version

   • 2010-12-04T12:23:20+00:00
6. 

   Roland Haas

   • edited description
   • changed status to closed

   • 2019-02-21T20:18:15+00:00
7. Log in to comment