Redmine files not executable, but log files are executable

Bernhard Froehlich decke at
Fri Feb 5 08:43:00 UTC 2010

On Fri, 05 Feb 2010 01:07:43 +0100, Miroslav Lachman <000.fbsd at>
> Hi,
> I am new to installation of www/redmine from ports. I am surprised that 
> all redmine files are not executable. Including files which should be 
> executed by startup script etc. (I mean files in script/ directory, 
> mainly script/server)
> These files are executables in the original source tar archive.
> What is more surprising is that after reinstall or upgrade of redmine, 
> there are executable bits set on logfiles, because of recursive chmod in

> redmine/Makefile:
> .for f in files log tmp public/plugin_assets
>          ${CHMOD} -R 755 ${WWWDIR}/${f}
> .endfor
> redmine/# find . -type f -perm +0111 -ls
> 321080   2 -rwxr-xr-x   1 www  www  374 May 28  2009 
> ./public/plugin_assets/README
>   14111   2 -rwxr-xr-x   1 www  www   36 Sep 13 14:10 ./files/
> 321079   2 -rwxr-xr-x   1 www  www   51 May 28  2009
>   14119   2 -rwxr-xr-x   1 www  www   36 Sep 13 14:10 ./log/
> I know that the first problem is caused by COPYTREE_SHARE in do-install:

> and I am asking if it is really necesarry to have all files set to 0444,

> I think those few files should be installed executable as in the 
> original archive.
> And chmod for directories should be not recursive to not set executable 
> bits on files from previous installation.
> So my proposal is use chmod without -R on directories only:
> .for f in files log tmp tmp/cache tmp/sessions tmp/sockets 
> public/plugin_assets
>          ${CHMOD} 755 ${WWWDIR}/${f}
> .endfor
> And to set 0554 on files in scripts/ directory
> .for f in about breakpointer console destroy generate plugin runner
>          ${CHMOD} 0555 ${WWWDIR}/script/${f}
> .endfor
> (and maybe some files in script/performance + script/process too)
> What you think about that?

Yes, that's true. All files should be non executable beyond /usr/local/www
so the COPYTREE_SHARE is right but the chmod -R should only be made for
directories and is obviously wrong.

Scripts shouldn't be beyond /usr/local/www. Honestly I've never used one
them so I'm not sure if they do work at all. It's probably better to have
them somewhere else but they do use relative paths to include code so they
are obviously not designed to work anywhere else outside of the redmine

The log directory should be in /var/log/redmine too so it looks like it's
to split the redmine directories up and have some deeper thought about the

I don't know what webserver redmine admins expect and how they integrate
into their configuration. Personally I've written a startscript that uses
www/rubygem-thin as webserver behind nginx but the out of the box version
mongrel. Haven't decided yet what to do but i could write startscripts for
common ruby servers and let the user choose with option he wants.

Thanks for the report and i will have a look at the issues soon.

Bernhard Fröhlich

More information about the freebsd-ports mailing list