Re: [Jetty-support] Setuid problems

[rgarret <RG...@co...>]

Claudio,

Thanks for your response but umask is optional. I put umask in but it had no
effect. My webapp is still undeployed after the setuid call. Also, I am
setting "startServerAsPrivileged" to true because I am trying to bind to
port 80.

I don't know how you are deploying your app but I am deploying using the
context deployeer as described here
http://docs.codehaus.org/display/JETTY/ContextDeployer. Perhaps if I was
deploying statically using the web application deployer this would not
happen. But I am deploying the way I am for a reason so I'm stuck.

Thanks,
Reece


Claudio Miranda wrote:
> 
> 
>     There is no umask at your jetty-setuid.xml. See mine for reference, it
> works fine.
> 
> <Configure id="Server" class="org.mortbay.setuid.SetUIDServer">
>   <Set name="startServerAsPrivileged">false</Set>
>   <Set name="umask">2</Set>
>   <Set name="uid">1000</Set>
> </Configure>
> 
>     And I have a "work" dir at jetty install dir, so jetty will use this
> "work" dir instead /tmp
>     The jetty install dir is owned by the 1000 user.
> 
> 
> rgarret wrote:
>> 
>> I have done all the setup and everything works great until the actual
>> setuid call is made. According to my logs when setuid is called all
>> context I have configured in jetty.xml (defined in $JETTY_HOME/contexts)
>> are undeployed and I am left with an empty web server. I have verified
>> that setuid does work but I can not figure out why it is undeploying my
>> contexts. Below I provide the command I use to run jetty, jetty.xml,
>> jetty-setuid.xml, and the log that shows my webapp (called personnel)
>> being undeployed. 
>> 
>> If anyone knows what's going on please help! 
>> 
>> sudo java -Djava.library.path=lib/ext -jar start.jar etc/jetty-setuid.xml
>> etc/jetty.xml
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Setuid-problems-tf4478069.html#a12867273
Sent from the Jetty Support mailing list archive at Nabble.com.