Ticket #2 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

Option to allow a delay between CVS executions

Reported by: Nikolas Coukouma Owned by: lele
Priority: minor Milestone: VersionOne
Component: tailor Version: 0.9
Keywords: Cc:

Description

I'm doing a massive CVS import, with history, and it seems that I'm killing the poor pserver. According to one source inetd assumes there's something wrong if it receives many requests for the same service repeatedly. So, it seems that checking out every revision of every file in a repository with a lengthy history (almost 4 or 5 years) is causing it to freak out.

What I've done for now is used the after-commit function to add a 10s delay between pulling changesets from CVS. It might be friendly if there was a config option to insert a short (0.5-1s?) pause between commands. I don't know how common this problem is, though. Any thoughts?

[1]

Change History

Changed 5 years ago by Lele Gaifax

  • status changed from new to closed
  • resolution set to fixed

Patch [847] and [848] introduced delay-before-apply, and integer that may be specified in a repository section as the number of seconds tailor should wait before applying each changeset, that is basically what was suggested as a working solution implemented with the after-commit hook.

Note: See TracTickets for help on using tickets.