Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Mylyn/Bugzilla Connector"

(Bugzilla Server Optimization)
(Preventing excessive logfile fill up)
Line 5: Line 5:
  
 
=== Preventing excessive logfile fill up ===
 
=== Preventing excessive logfile fill up ===
* When running /bugzilla/ locally, one can prevent Mylin  filling up the log files by adding this to httpd.conf:
+
* When running /bugzilla/ locally, one can prevent Mylyn filling up the log files by adding this to httpd.conf:
 
<code>
 
<code>
 
<DirectoryMatch /bugzilla/ ><br />
 
<DirectoryMatch /bugzilla/ ><br />
&nbsp;&nbsp;&nbsp;&nbsp;BrowserMatchNoCase mylyn mylin=1 <br />
+
&nbsp;&nbsp;&nbsp;&nbsp;BrowserMatchNoCase mylyn mylyn=1 <br />
 
</DirectoryMatch> <br />
 
</DirectoryMatch> <br />
CustomLog "/private/var/log/httpd/access_log" combined env=!mylin<br />
+
CustomLog "/private/var/log/httpd/access_log" combined env=!mylyn<br />
 
</code>
 
</code>
  

Revision as of 12:36, 23 July 2007


Bugzilla Server Optimization

  • Cached Repository Configuration - This page describs the solution taken by Eclipse.org webmasters to reduce the bandwidth requirements due to Mylyn clients updating their repository configuration.

Preventing excessive logfile fill up

  • When running /bugzilla/ locally, one can prevent Mylyn filling up the log files by adding this to httpd.conf:

<DirectoryMatch /bugzilla/ >
    BrowserMatchNoCase mylyn mylyn=1
</DirectoryMatch>
CustomLog "/private/var/log/httpd/access_log" combined env=!mylyn

Users

Developer Resources

Mylyn Offline Refactoring

Back to the top