Clearcase 快照视图上次更新是什么时候?

发布于 2024-11-11 17:54:02 字数 2029 浏览 2 评论 0原文

我想找到最后更新 Clearcase 快照视图的时间戳。我指的是最后一次“cleartool 更新”开始的时间。

或者,换句话说,如果我要创建一个带有时间戳的动态视图,我应该使用什么时间戳来使其完全等同于给定的快照视图?

我能想到的唯一方法是查找名为 update.[timestamp].updt 的日志文件,该文件在每次视图更新时写入快照视图目录的根目录。但在某些情况下,我无权访问该文件。还有别的办法吗?

以下命令看起来很接近,但我不确定这是否是我想要的 -

ewat> cleartool lsview -prop -full ewatkins_11122_s_ewatkin4
  ewatkins_11122_s_ewatkin4 /scfs3/vws_u/ewatkins/ewatkins_11122_s_ewatkin4.vws
Created 19-Apr-11.23:42:13 by ewatkins.cdev@dscddy02
Last modified 02-Jun-11.16:28:45 by [email protected]
Last accessed 02-Jun-11.16:28:45 by [email protected]
Last read of private data 02-Jun-11.16:28:45 by [email protected]
Last config spec update 25-Apr-11.15:50:13 by [email protected]
Last view private object update 02-Jun-11.16:28:45 by [email protected]
Text mode: unix
Properties: snapshot readwrite
Owner: arbor.hyperion.com/ewatkins : rwx (all)
Group: arbor.hyperion.com/cdev : r-x (read)
Other:                  : r-x (read)
Additional groups: arbor.hyperion.com/essbase_prerel

上面的输出是在我执行快照更新后立即获取的。您可以看到上次修改、上次访问、上次读取和上次更新都已设置为快照更新完成的时间 - 02-Jun-11.16:28:45。

这次不太像我想要的。假设快照更新需要几分钟。如果我使用此时间戳创建动态视图,则动态视图将包含在更新运行的几分钟内签入的所有新文件。

除非我有 update.[timestamp].updt 文件,否则我会运气不好吗?

I want to find the timestamp when a clearcase snapshot view was last updated. By this, I mean the time when the last "cleartool update" was started.

Or, said another way, if I was going to make a dynamic view with a timestamp, what timestamp should I use to make it exactly equivalent to a given snapshot view?

The only way I can come up with is to look for the log file called update.[timestamp].updt that is written to the root of the snapshot view directory on every view update. But in some cases, I don't have access to this file. Is there another way?

The following command looks like it comes close, but I'm not sure if it's what I want -

ewat> cleartool lsview -prop -full ewatkins_11122_s_ewatkin4
  ewatkins_11122_s_ewatkin4 /scfs3/vws_u/ewatkins/ewatkins_11122_s_ewatkin4.vws
Created 19-Apr-11.23:42:13 by ewatkins.cdev@dscddy02
Last modified 02-Jun-11.16:28:45 by [email protected]
Last accessed 02-Jun-11.16:28:45 by [email protected]
Last read of private data 02-Jun-11.16:28:45 by [email protected]
Last config spec update 25-Apr-11.15:50:13 by [email protected]
Last view private object update 02-Jun-11.16:28:45 by [email protected]
Text mode: unix
Properties: snapshot readwrite
Owner: arbor.hyperion.com/ewatkins : rwx (all)
Group: arbor.hyperion.com/cdev : r-x (read)
Other:                  : r-x (read)
Additional groups: arbor.hyperion.com/essbase_prerel

The above output was taken right after I did a snapshot update. You can see that last modified, last accessed, last read, and last update have all been set to the time when the snapshot update finished -- 02-Jun-11.16:28:45.

This time is not quite what I want. Assume the snapshot update takes several minutes. If I make a dynamic view with this timestamp, the dynamic view will have any new files that were checked in during the several minutes while the update was running.

Am I out of luck unless I have the update.[timestamp].updt file?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

怎言笑 2024-11-18 17:54:02

我想我回答了我自己的问题 -

update..updt 中的时间戳是“cleartool update”开始的时刻,但它是本地计算机上的时间 - 可能与 Clearcase 服务器计算机上的时间不同。
例如,我的两台机器上的时间相差大约3分钟。所以这个时间戳不是我要找的。当然,我可以只使用 NTP 来同步时间,但我发现了其他有趣的东西......

cleartool update”不会更新“上次配置规范更新”时间。

cleartool setcs -current”确实将“上次配置规范更新”时间更新为更新开始的那一刻。
由于我们使用 Hudson 来管理快照视图,并且 Hudson clearcase 插件执行 setcs -current 操作,那么我们很幸运!
“上次配置规范更新”时间正是我想要的,甚至是clearcase服务器上的时间,而不是本地主机上的时间!

I think I answered my own question --

The timestamp in the update.<timestamp>.updt is the moment that the "cleartool update" was started, but it's the time on the local machine - which may be different from the time on the clearcase server machine.
For instance, the time on my two machines are different by about 3 minutes. So this timestamp is not what I'm looking for. Of course, I could just use NTP to synchronize the times, but I found something else interesting...

"cleartool update" does not update the "Last config spec update" time.

"cleartool setcs -current" DOES update the "Last config spec update" time to the moment the update started.
And since we're using Hudson to manage our snapshot views, and the Hudson clearcase plugin does setcs -current, then we are in luck!
The "Last config spec update" time is exactly what I want, and it's even the time on the clearcase server, not the local host!

软糖 2024-11-18 17:54:02

根据我的测试,我认为您最终不会得到比“上次配置规范更新”日期更新的任何版本(而上次修改日期是 完全由操作系统管理

所以你应该可以使用“最后一个配置规范”进行动态视图更新“基于时间的规则

请参阅 IBM 手册页“快照视图如何更新"

更新操作说明更新不是即时的。当您的视图更新时,其他开发人员可能会签入您视图的加载规则选择的元素的新版本。为了避免加载不一致的版本集,更新操作会忽略 VOB 中满足以下两个条件的版本:

  • 版本在更新开始后签入
  • 现在由涉及最新版本标签的配置规范规则选择版本。

此更新针对网络中不同主机上的系统时钟可能不同步(即时钟有偏差)的可能性进行了调整。

From what I tested, I don't think that you would end up with any version newer than the "last config spec update" date (while the last modified date is entirely managed by the OS)

So you should be ok doing a dynamic view with the "Last config spec update" time-based rule.

See the IBM man page "How snapshot views are updated"

The update operation accounts for the fact that updates are not instantaneous. As your view is updated, other developers may check in new versions of elements that the load rules for your view select. To avoid loading an inconsistent set of versions, the update operation ignores versions in the VOB that meet both of the following conditions:

  • The version was checked in after the moment the update began.
  • The version is now selected by a config spec rule that involves the LATEST version label.

The update adjusts for the possibility that the system clocks on different hosts in a network may not be synchronized (that is, clocks are skewed).

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文