roller-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Mazza (JIRA)" <>
Subject [jira] [Commented] (ROL-2016) roller-startup.log not created on startup
Date Tue, 10 Jun 2014 00:47:02 GMT


Glen Mazza commented on ROL-2016:

It would be nice if we didn't need the roller-startup.log at all, just rely on the servlet-specific
log file (catalina.out) and the regular roller.log.  For the few types of error messages that
could occur before roller.log gets initialized, perhaps output them to the terminal where
they would end up getting picked up by the catalina.out (or whatever servlet container you're
using version of that)?

What happens if it cannot create that roller-startup file on your machine due to lack of access
to the / folder?  Does Roller fry?  That would be bug I would say.  If Roller happily continues
on to your roller.log file, then this shouldn't be an issue due to the fact that roller-startup.log
is almost always empty anyway.

This may not be a coding issue but a documentation (Install Guide) one, namely add a blurb
about defining log4j.appender.roller-startup.File to point to an accessible location.  'Course,
if Roller could read the at that stage, it might as well use the
regular roller.log anyway.

> roller-startup.log not created on startup
> -----------------------------------------
>                 Key: ROL-2016
>                 URL:
>             Project: Apache Roller
>          Issue Type: Bug
>          Components: Installation & Configuration
>    Affects Versions: 5.0.3
>         Environment: Tomcat
>            Reporter: Greg Huber
>            Assignee: Greg Huber
>            Priority: Minor
> When starting in tomcat I get a permission denied on the roller-startup.log.

This message was sent by Atlassian JIRA

View raw message