On Tue, Apr 14, 2015 at 4:38 PM, Jesse McConnell <[email protected]>
wrote:

> Not deprecated or anything like that, we just resolved a couple of
> issues with this on the forthcoming Jetty 9.3 release so certainly a
> feature we will continue to support.
>

I noticed that std out/err logs configured by the logging module end up
owned by root, was this an issue that was fixed?

This happens when I use suid and logging with the below config (request log
is not owned by root??)

Best, Tim


<?xml version="1.0"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "
http://www.eclipse.org/jetty/configure_9_0.dtd";>


<!-- =============================================================== -->
<!-- Configure stderr and stdout to a Jetty rollover log file        -->
<!-- this configuration file should be used in combination with      -->
<!-- other configuration files.  e.g.                                -->
<!--    java -jar start.jar etc/jetty-logging.xml                    -->
<!-- =============================================================== -->
<Configure id="logging" class="org.eclipse.jetty.util.log.Log">

    <!-- Jetty console log
(.sierra-data/server/log-jetty-console-yyy_mm_dd.txt) -->

    <New id="ServerLog" class="java.io.PrintStream">
      <Arg>
        <New class="org.eclipse.jetty.util.RolloverFileOutputStream">
          <Arg><Property name="jetty.base"
default="."/>/../logs/jetty-stderrout-yyyy_mm_dd.txt</Arg>
          <Arg type="boolean">false</Arg>
          <Arg type="int">90</Arg>
          <Arg><Call class="java.util.TimeZone"
name="getTimeZone"><Arg>GMT</Arg></Call></Arg>
          <Get id="ServerLogName" name="datedFilename"/>
        </New>
      </Arg>
    </New>

    <Get name="rootLogger">
      <Call name="info"><Arg>Redirecting stderr/stdout to <Ref
refid="ServerLogName"/></Arg></Call>
    </Get>
    <Call class="java.lang.System" name="setErr"><Arg><Ref
refid="ServerLog"/></Arg></Call>
    <Call class="java.lang.System" name="setOut"><Arg><Ref
refid="ServerLog"/></Arg></Call>

</Configure>





>
> I am not sure what is missing with that in the documentation though,
> that is odd...looking into that now and will see about restoring it.
> --
> jesse mcconnell
> [email protected]
>
>
> On Tue, Apr 14, 2015 at 3:23 PM, Scott Koranda <[email protected]> wrote:
> > Hello,
> >
> > I am using Jetty 9.2.10.v20150310 on RHEL 7.
> >
> > I have been following the documentation at
> >
> > http://www.eclipse.org/jetty/documentation/current/index.html
> >
> > I can not find in that set of documentation details on the setuid
> > functionality that is described in Chapter 20 of the documentation for
> > version 9.2.1 at
> >
> > http://www.eclipse.org/jetty/documentation/9.2.1.v20140609/setuid.html
> >
> > If I am simply missing the setuid page in the current documentation I
> > would be grateful if you could point me to it.
> >
> > If the setuid documentation is missing on purpose, does that imply the
> > functionality is being deprecated or will not be "supported"?
> >
> > Thanks,
> >
> > Scott K
> > _______________________________________________
> > jetty-users mailing list
> > [email protected]
> > To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> > https://dev.eclipse.org/mailman/listinfo/jetty-users
> _______________________________________________
> jetty-users mailing list
> [email protected]
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/jetty-users
>
_______________________________________________
jetty-users mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users

Reply via email to