Re: Update : Run each component of application as different user working - except stop command

2016-05-04 Thread Manoj Samel
Hi Josh, Mapreduce in secured cluster already works like this - the jobs are run using end user logins - not as some admin login. This is key security feature and ensures no rogue jobs can interfere with each other or do some linux level access. So this feature will bring slider component

Re: Update : Run each component of application as different user working - except stop command

2016-05-04 Thread Josh Elser
Manoj Samel wrote: 1. I have loggedhttps://issues.apache.org/jira/browse/SLIDER-1114 to describe the use case in detail as a new feature request. Josh - regarding your suggestion on launching each component as separate app; I have added a comment in Jira on why that is not feasible - hope that

Update : Run each component of application as different user working - except stop command

2016-05-02 Thread Manoj Samel
; > but loops infinitely. I.e. without it being setuid or doing other > execle() > > etc. Even with the simple C binary, I see above behavior. So something > > different about using a executable rather than Java command as component > > ??? Should I execute the C binary c

Re: (2nd attempt) Need Help !: Run each component of application as different user

2016-04-25 Thread Billie Rinaldi
??? Should I execute the C binary component in different manner ? > > Any guidance on this will be really appreciated > > > Thanks, > > Manoj > > -- Forwarded message -- > From: Manoj Samel <manojsamelt...@gmail.com> > Date: Thu, Apr 2

Re: (2nd attempt) Need Help !: Run each component of application as different user

2016-04-25 Thread Josh Elser
l be really appreciated Thanks, Manoj -- Forwarded message -- From: Manoj Samel<manojsamelt...@gmail.com> Date: Thu, Apr 21, 2016 at 2:40 PM Subject: Need Help !: Run each component of application as different user To: dev@slider.incubator.apache.org Hi, See use case back

(2nd attempt) Need Help !: Run each component of application as different user

2016-04-22 Thread Manoj Samel
Thanks, Manoj -- Forwarded message -- From: Manoj Samel <manojsamelt...@gmail.com> Date: Thu, Apr 21, 2016 at 2:40 PM Subject: Need Help !: Run each component of application as different user To: dev@slider.incubator.apache.org Hi, See use case background below I have implemente

Re: Need Help !: Run each component of application as different user

2016-04-21 Thread Manoj Samel
Forgot to mention some digging I did ... initially to check the status check failures ... In the component's python management script, for the status check call, I had the status use the check_process_status() function provided by slider and used in many examples ; like below ... def

Need Help !: Run each component of application as different user

2016-04-21 Thread Manoj Samel
Hi, See use case background below I have implemented option 2 mentioned below (as a C program deployed on nodes as setuid root binary). Need help in debugging issue I am seeing Without the setuid option, the execution is 1. Launch Slider AM as user "A" 2. Launch java component using command

Need help !: Run each component of application as different user

2016-04-21 Thread Manoj Samel
Hi, See use case background below I have implemented option 2 below. Need help in debugging issue I am seeing Without the setuid option, the execution is 1. Launch Slider AM as user "A" 2. Launch java component using command like "java -cp ". These run as user "A" as well With setuid

Re: Run each component of application as different user

2016-04-11 Thread Manoj Samel
Any thoughts ? Feedback ? On Fri, Apr 8, 2016 at 10:30 AM, Manoj Samel wrote: > Hello, > > Environment is slider .80 on Hadoop 2.6 secured cluster > > A component is launched for each distinct user of the service (via > upgrade). E.g. when user A accesses service, do a

Run each component of application as different user

2016-04-08 Thread Manoj Samel
Hello, Environment is slider .80 on Hadoop 2.6 secured cluster A component is launched for each distinct user of the service (via upgrade). E.g. when user A accesses service, do a "upgrade" and create a component for user A. When user B comes, create another component for user B etc. At