Some modules use the same hook and therefore are 'called' in succession. Sometimes you would like (need) a particular module to fire after or before other modules. An example is the XML site map module that would best fire after the pathauto module to ensure that the site map contains the final version of the urls used for pages in your site. There are a number of ways to manage this -

one is to access the database directly and alter the weight of modules directly. The better way is to use the Utility module (http://drupal.org/project/util)

This surfaces a module weight for each module.

The Utility Module contains a set of utilities ( ) that enable you to carryout some routine tasks without having to code them yourself or resort to DB access directly. see http://drupal.org/project/util

Note that the project page implies there are loads of great utilities included - these are only available in the dev release -6.x-3.x-dev.

The 6.x-2.3 only contains the module weight and permissions fieldset manager.

The utilities of particular interest are:

• Module weight: this provides access to the module weight in the modules listing and enables you to determine the order of 'firing' of certain key modules when they use the same hook.
• Log_Clear: The error log clearing facilities that attach to the filter log fieldset. This enables you to clear log entries according to the filter - great for clearing page not found errors you have dealt with for example.
• Permissions and modules get collapsible fields sets and useage values. This makes the listing pages easier to use