merkisoft commented on PR #809:
URL: https://github.com/apache/logging-log4j2/pull/809#issuecomment-1847522126
the problem is that althought the logs dir exists, you call to create it and
java security manager kicks in and it requires these two lines (i only had the
2nd initially, because in my view log4j should not attempt to write the dir):
permission java.io.FilePermission "${user.dir}/logs", "read,write";
// <<< this was missing and grants mkdir on the parent
permission java.io.FilePermission "${user.dir}/logs/-", "read,write";
config - using log4j 1-2 bridge:
log4j.appender.file=org.apache.log4j.DailyRollingFileAppender
log4j.appender.file.File=logs/kurs.log
anyhow: the java security manager / policy files are not often used and are
apparently on the way out, no need to fix - hopefully the one who has the same
issue finds this comment :-)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
