I wanted to use %d{yyMM}/%d{dd} and it didn't work for the same reason, but %{yyMM/dd} works fine. No idea if it applies to your case. I don't understand why only the first date format gets considered for rollover. IMHO it's a bug, while taking the *union of all date specifiers* would be just right. On Thu, Oct 12, 2017 at 9:26 PM, QOS.CH (JIRA) <noreply-jira@qos.ch> wrote:

Sean Nelson created LOGBACK-1346: ------------------------------------

Summary: Set daily rollovers without full date together in the fileNamePattern Key: LOGBACK-1346 URL: https://jira.qos.ch/browse/LOGBACK-1346 Project: logback Issue Type: Improvement Reporter: Sean Nelson Assignee: Logback dev list Priority: Minor

I want to set up a daily rollover with the following fileNamePattern: * /path/to/rolling_logs/%d\{yyyy-MM,aux}/%d\{dd}/log_name.%i.log

When I try this, I get an error explaining, '*T**he date format in FileNamePattern will result in collisions in the names of archived log files*.' This format would not actually result in naming collisions. The only workaround I've found is to include the full date as part of the filename, e.g.: * /path/to/rolling_logs/%d\{yyyy-MM,aux}/%d\{dd,aux}/log_name.%d.%i.log

If there is some other workaround that I'm not aware of, please advise.

-- This message was sent by Atlassian JIRA (v7.3.1#73012) _______________________________________________ logback-dev mailing list logback-dev@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-dev