Edgewall Software

Changes between Version 366 and Version 367 of TracInstall


Ignore:
Timestamp:
Nov 21, 2013, 3:51:37 AM (7 years ago)
Author:
Ryan J Ollos
Comment:

Updated for fix put in place in #11329.

Legend:

Unmodified
Added
Removed
Modified
  • TracInstall

    v366 v367  
    232232Also note that the values you specify here can be changed later by directly editing the [TracIni conf/trac.ini] configuration file.
    233233
    234 When selecting the location of your environment, make sure that the filesystem on which the environment directory resides supports sub-second timestamps (i.e. **not** `ext2` or `ext3` on Linux), as the modification time of the `conf/trac.ini` file will be monitored to decide whether an environment restart is needed or not. A too coarse-grained timestamp resolution may result in inconsistencies.
     234When selecting the location of your environment, make sure that the filesystem on which the environment directory resides supports sub-second timestamps (i.e. **not** `ext2` or `ext3` on Linux), as the modification time of the `conf/trac.ini` file will be monitored to decide whether an environment restart is needed or not. A too coarse-grained timestamp resolution may result in inconsistencies in Trac < 1.0.2 (though the best advice is to opt for a platform with sub-second timestamp resolution when possible regardless of the version of Trac you are running).
    235235
    236236Finally, make sure the user account under which the web front-end runs will have '''write permissions''' to the environment directory and all the files inside. This will be the case if you run `trac-admin ... initenv` as this user. If not, you should set the correct user afterwards. For example on Linux, with the web server running as user `apache` and group `apache`, enter: