Re: [Daemon] StdOut and StdErr use extra newline

[Gil Baruch]

Maybe I was misunderstood, each line ends with two newlines not just the
end of the file...

So there's a gap of one empty line between every two lines...

Thanks
GBa.

On Thu, Mar 22, 2018, 23:32 Gil Baruch <gilbaruch.m...@gmail.com> wrote:

> I'm using the daemon to wrap my Jetty based service. I've redirected
> stdout and stderr to the Daemon via the relevant configuration params.
>
> However, both files end up with 2 newline characters (/r/n/r/n) which
> results in a very unreadable log... especially when dealing with
> stacktraces...
>
> Any idea what could cause that?
>
> BTW, when using Jetty without the wrapper, Jetty's stdout and err do not
> suffer from this behavior.
>
> thanks,
> GBa.
>

[Daemon] StdOut and StdErr use extra newline

[Gil Baruch]

I'm using the daemon to wrap my Jetty based service. I've redirected stdout
and stderr to the Daemon via the relevant configuration params.

However, both files end up with 2 newline characters (/r/n/r/n) which
results in a very unreadable log... especially when dealing with
stacktraces...

Any idea what could cause that?

BTW, when using Jetty without the wrapper, Jetty's stdout and err do not
suffer from this behavior.

thanks,
GBa.

Re: [daemon] Problem with Working Directory

[Gil Baruch]

OMG, was looking for it for so long... no idea how I missed it, I went over
this page at least 5 times...

thanks a lot, worked flawlessly!
GBa.



On Wed, Mar 7, 2018 at 6:34 AM, Gary Gregory <garydgreg...@gmail.com> wrote:

> Have you tried using --StartPath? See
> https://commons.apache.org/proper/commons-daemon/procrun.html
>
> Gary
>
> On Tue, Mar 6, 2018 at 2:07 PM, Gil Baruch <gilbaruch.m...@gmail.com>
> wrote:
>
> > Seems like I hit a well known issue although I couldn't find
> documentation
> > about it in the FAQ (unfortunately).
> >
> > It seems that Java does not fully support changing the working directory
> > (AKA system property 'user.dir').
> >
> > Some functionality, such as new File(relativePath) will not be affected
> by
> > a change of 'user.dir' system property and instead, the file path would
> be
> > constructed out of the actual working directory that the JVM started
> from.
> >
> > However, when using the Daemon, I cannot specify the directory from where
> > to perform the execution of the JVM...
> >
> > what am I missing?
> >
> > thanks,
> > GBa.
> >
>

[daemon] Problem with Working Directory

[Gil Baruch]

Seems like I hit a well known issue although I couldn't find documentation
about it in the FAQ (unfortunately).

It seems that Java does not fully support changing the working directory
(AKA system property 'user.dir').

Some functionality, such as new File(relativePath) will not be affected by
a change of 'user.dir' system property and instead, the file path would be
constructed out of the actual working directory that the JVM started from.

However, when using the Daemon, I cannot specify the directory from where
to perform the execution of the JVM...

what am I missing?

thanks,
GBa.