[Cruisecontrolrb-users] permission problem

12 views
Skip to first unread message

Christopher Gaudig

unread,
Sep 28, 2010, 10:07:33 AM9/28/10
to cruisecont...@rubyforge.org
Hi!

When I run my build script manually (in a shell) everything works fine.
But when I try to let CruiseControl.rb run it, I get a permission error.

It seems as though CC has different user permissions when running the
script from the ones I have when running it manually.

A dirty fix is to start CC with sudo, but I would like to run it as a
normal user, if possible.

Any ideas would be greatly appreciated! Thanks!

Regards
Chris


--
Christopher Gaudig
Underwater & Space Robotics

DFKI Bremen
Robotics Innovation Center
Robert-Hooke-Straße 5
28359 Bremen, Germany

Phone: +49 (0)421 178-45 4119
Fax: +49 (0)421 178-45 4150
E-Mail: christoph...@dfki.de

Web: http://www.dfki.de/robotik
-----------------------------------------------------------------------
German Research Center for Artificial Intelligence
Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. W. Wahlster (Vorsitz), Dr.
W. Olthoff
Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
USt-Id.Nr.: DE 148646973
Steuernummer: 19/673/0060/3
_______________________________________________
Cruisecontrolrb-users mailing list
Cruisecont...@rubyforge.org
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users

Chad Woolley

unread,
Sep 28, 2010, 12:12:07 PM9/28/10
to cruisecont...@rubyforge.org
On Tue, Sep 28, 2010 at 7:07 AM, Christopher Gaudig
<christoph...@dfki.de> wrote:
> Hi!
>
> When I run my build script manually (in a shell) everything works fine. But
> when I try to let CruiseControl.rb run it, I get a permission error.
>
> It seems as though CC has different user permissions when running the script
> from the ones I have when running it manually.
>
> A dirty fix is to start CC with sudo, but I would like to run it as a normal
> user, if possible.
>
> Any ideas would be greatly appreciated! Thanks!

It should run as whatever user you started it as. Look closely and
understand how it is starting, and as what user. Make a dummy build
which drops files in /tmp, and inspect permissions. Check your umask.

Reply all
Reply to author
Forward
0 new messages