On Wed, May 08, 2013 at 09:51:26PM -0600, Bob Proulx wrote:
> > > Check 'sudo -l' to list the user's sudo status dump?
> >
> > User rob may run the following commands on this host:
> > (ALL) ALL
>
> That doesn't seem sufficient for Wheezy. I don't see secure_path in
> that output for example.
Rob Owens wrote:
> I replaced libpam-ldap with libpam-ldapd and now sudo and su are both
> working. Not sure why, but I"ll dig into it if I get some time.
Glad to hear that it is working. I am not an ldap expert so don't
know either.
I am going to comment on your previous anyway.
> But I'll gi
On Wed, May 08, 2013 at 08:18:25PM -0400, Rob Owens wrote:
> On Wed, May 08, 2013 at 11:30:25AM -0600, Bob Proulx wrote:
> > Rob Owens wrote:
> > > Currently my system seems to be working fine except that I can't su or
> > > sudo from my regular user. I can log in as root. My users are all LDAP
>
On Wed, May 08, 2013 at 11:30:25AM -0600, Bob Proulx wrote:
> Rob Owens wrote:
> > Currently my system seems to be working fine except that I can't su or
> > sudo from my regular user. I can log in as root. My users are all LDAP
> > authenticated.
>
> First, I don't know. But it does seem lik
Rob Owens wrote:
> Currently my system seems to be working fine except that I can't su or
> sudo from my regular user. I can log in as root. My users are all LDAP
> authenticated.
First, I don't know. But it does seem like there might be an LDAP
interaction with sudo. Are you using "sudo-lda
I just upgrade from Squeeze to Wheezy. I haven't rebooted yet for fear
that things will get worse...
Currently my system seems to be working fine except that I can't su or
sudo from my regular user. I can log in as root. My users are all LDAP
authenticated.
I took care to properly update the
2005/9/30, Wang Xu <[EMAIL PROTECTED]>:
> Hi All,
>
> I have 2 linux computer, one is running testing, and the other is running
> unstable.
>
> Now the sid one cannot use `su' to change from root to any user, including
> itself.
additional information:
I found there were some problems about wheel
2005/9/30, Stephen Cormier <[EMAIL PROTECTED]>:
> Try upgrading the login package I think you may have run into bug
> #330291.
>
Thank you!
However, the version of my `login' has already been `4.0.12-5' as
suggested in `Bug #330291'
--
==
WANG,
On September 29, 2005 09:49 pm, Wang Xu wrote:
> Hi All,
>
> I have 2 linux computer, one is running testing, and the other is
> running unstable.
>
> Now the sid one cannot use `su' to change from root to any user,
> including itself.
>
> cannot su - xx
> cann
Hi All,
I have 2 linux computer, one is running testing, and the other is running
unstable.
Now the sid one cannot use `su' to change from root to any user, including
itself.
cannot su - xx
cannot su xx
cannot su xx -c 'command'
but the 'su -c' is improtant for the ac
> My su doesn't give that error. It just says "Permission denied" when i try
> anything that would involve accessing the contents of the current
> directory. No errors though, and pwd works fine.
Sorry, my mistake. I forgot, I only see this on my girlfriend's machine, and
I assume its because she
On Sat, 22 May 1999, Rob wrote:
> You get these errors (sometimes) when suing to a normal user from another
> normal user, eg:
>
> /home/jim has permission 700 (drwx--) and I'm in /home/jim (and I AM jim
> ;) I do 'su bob', enter the correct password, and I get those messages.
> Which makes s
Yeah, that would be a more likely reason. However, messing up permissions
could do that as well.
Andrew.
---
Andrei S. Ivanov
[EMAIL PROTECTED]
[EMAIL PROTECTED]
UIN 12402354
http:
> The only time i can recall seeing those errors is when the cwd is moved or
> removed. Just now, i created a dir 'test', cd-ed to it as root, removed it
> from another tty, and su-ed to a normal user. Sure enough, there's the
> error. Even if it's removed and remade from the other tty before su-in
On Fri, 21 May 1999, Andrei Ivanov wrote:
> > shell-init: could not get current directory: getcwd: cannot access parent
> > directories.
>
> Check your permissions on . and .. directories. They should be
> chmod'd and chown'd as below.
>
> drwxr-xr-x 2 root root 1024 May 2 19:2
> shell-init: could not get current directory: getcwd: cannot access parent
> directories.
>
> Best wishes,
> Chip
Check your permissions on . and .. directories. They should be
chmod'd and chown'd as below.
drwxr-xr-x 2 root root 1024 May 2 19:21 .
drwxr-xr-x 5 root roo
Hi,
Can anyone tell me why I get the following message after su to a user
from root? Thanks!
shell-init: could not get current directory: getcwd: cannot access parent
directories.
Best wishes,
Chip
17 matches
Mail list logo
