> sifting appender are not also logged to error.log), what is the best way to
> to it?
>
> John
>
>
>
>
> From: Chetan Mehrotra <chetan.mehro...@gmail.com>
> Sent: Thursday, September 14, 2017 1:23:45 AM
> To: users@sling
tember 14, 2017 1:23:45 AM
To: users@sling.apache.org
Subject: Re: Directing Sling job logging output to separate files?
While providing a custom logback.xml do remember to add Sling specific
handlers [1]. Otherwise OSGi integration of logging config would not
work as expected
Chetan Mehrotra
[1
th,
> Path damLogPath) {
> try (BufferedReader reader = Files.newBufferedReader(logPath,
> StandardCharsets.UTF_8)) {
> final SlingResourceProvider storageProvider = new
> SlingResourceProvider();
> storageProvider.setResolver(resolver);
>
.cancelled();
> }
>
> private void saveLog(ResourceResolver resolver, Path logPath, Path
> damLogPath) {
> try (BufferedReader reader = Files.newBufferedReader(logPath,
> StandardCharsets.UTF_8)) {
> final SlingResourceProvider storageProvider =
le to move build log " + logPath + " to DAM resource
" + damLogPath, e);
}
}
}
____________
From: Robert Munteanu <romb...@apache.org>
Sent: Friday, September 8, 2017 1:13:02 AM
To: users@sling.apache.org
Subject: Re: Directing Sling job
tember 8, 2017 1:13:02 AM
To: users@sling.apache.org
Subject: Re: Directing Sling job logging output to separate files?
Hi John,
On Fri, 2017-09-08 at 05:28 +, John Logan wrote:
> Hi,
>
>
> I'm using the Sling job manager to handle some long running tasks,
> and would like to
Hi John,
On Fri, 2017-09-08 at 05:28 +, John Logan wrote:
> Hi,
>
>
> I'm using the Sling job manager to handle some long running tasks,
> and would like to direct the log output for each job to its own file
> at a job-specific path. Is there a straightforward way to achieve
> this?
If
Hi,
I'm using the Sling job manager to handle some long running tasks, and would
like to direct the log output for each job to its own file at a job-specific
path. Is there a straightforward way to achieve this?
Thanks!
John Logan
