No, sorry. I just checked that again and I can yum. I guess I remembered that incorrectly.
But the thing is, I'm worried that I have all this stuff set up and working --postgresql, virtualenv, psycopg2 in root; then if I try another install under joshmoe it could cause even more more chaos. On Sun, Sep 29, 2013 at 1:01 PM, Augori <aug...@gmail.com> wrote: > You're right, I installed the virtualenv as user root into /root. > > The reason for this is that I can't run 'yum' and probably many of the > other commands from joshmoe, so I gave up on that route. But I'm open for > suggestions...do you think it would be better to try to get access to these > commands? > > > On Sun, Sep 29, 2013 at 12:46 PM, Adrian Klaver > <adrian.kla...@gmail.com>wrote: > >> On 09/29/2013 09:38 AM, Augori wrote: >> >>> Thanks to Adrian for pointing to this site. >>> http://toomuchdata.com/2012/**06/25/how-to-install-python-2-** >>> 7-3-on-centos-6-2/<http://toomuchdata.com/2012/06/25/how-to-install-python-2-7-3-on-centos-6-2/> >>> I was able to get the virtual environment set up and install psycopg2 >>> from there. Now things seem to be working well when I'm logged in as >>> root. >>> >>> But I need to be able to use the virtualenv as a non-root user, joshmoe. >>> (And start/stop postgresql as this other user) >>> >> >> I've found a good many examples of sudoer statements. But I can't >>> figure out the syntax that will make this work. I'm hoping once I get >>> this one, I'll be able to give access to statements like 'service >>> postgresql status' and so forth. >>> >> >> >> Looks to me you installed the virtualenv as user root into /root. Why not >> install the virtualenv as joshme into /joshme? Then you avoid the sudo >> problems all together. It also one of the benefits of virtualenv you can >> run programs as an ordinary user and not make them system wide. >> >> >> -- >> Adrian Klaver >> adrian.kla...@gmail.com >> > >
