We have a build system that creates and installs RPM's... The installation must be done as root, and leads to mixed ownership of files if we only sudo that portion. That is what we are currently doing and it causes us lots of problems.
For example, some RPMS we build from our own source and some we use from 3rd parties... When doing the build, we end up with files owned by the developer and the RPM install has files owned by root. We can get around this with a lot of calls to "chown" but that makes the build files pretty nasty. --jah -----Original Message----- From: Anderson, Rob (Global Trade) [mailto:[EMAIL PROTECTED] Sent: Wednesday, 14 February, 2007 11:34 To: Ant Users List Subject: RE: Switching to 'root' user What are you trying to accomplish as root? Running ant as root should probably not be necessary. There are probably only a few commands that need to run as root. I would suggest configuring sudo to only allow execution of those specific commands (with NOPASSWD), and in your build.xml file use the exec task to run sudo. -Rob Anderson > -----Original Message----- > From: jason heddings [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 14, 2007 9:15 AM > To: 'Ant Users List' > Subject: Switching to 'root' user > > Is it possible to run 'ant' as a regular user, but in the > build file change the process to run as 'root' instead? I > could just prefix the ant command with 'sudo' but I'd like to > try to accomplish this "behind the scenes" of our developers. > > Thanks, > --jah > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] For > additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
