public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Ray Olszewski <ray@comarre.com>
To: linux-newbie@vger.kernel.org
Subject: Re: setgid: Operation not permitted
Date: Mon, 29 Dec 2003 08:26:49 -0800	[thread overview]
Message-ID: <5.1.0.14.1.20031229081228.01f1b6a8@celine> (raw)
In-Reply-To: <3FF02337.D6169DC9@gelm.net>

At 07:51 AM 12/29/2003 -0500, chuck gelm net wrote:
>Howdy:
>
>  I broke something on my file server and now I can no longer
>'su' (root) remotely.  When I try I get this error:
>
>setgid: Operation not permitted
>
>  Often I logged on remotely and issued
>
>su
>cd /hde3
>chmod -R 775 *
>chgrp -R users
>
>So that I could 'rw' the files in that directory
>from any of my Windows workstations.
>OBTW, ("/hde3" is /dev/hde3).
>
>  What might I have done and how do I fix it?
>
>  The system is an old amd-k6-266 running
>Slackware-8.0 kernel 2.4.19 configured as a file server
>using nfs and samba.


"What might I have done" is always a tough question to answer. I'm assuming 
a couple of details that you left out, namely that (a) the message you 
quote occurs right after you enter the root password, with nothing in 
between, and (b) the su then fails, leaving you at whatever userid you were 
at before entering the "su" command. Also that the exact command you enter 
is "su" (not, for example, "su -") and that it is entered at a 
normal-looking command prompt.

I'd check these things:

1. In /etc/passwd, is root still group 0?
2. In /etc/group, is group 0 present and named "root"?
3. Are any relevant filesystems misset to be read-only? (If your system 
even has an hde drive, it is unusual in some respect.)
4. Did anything odd get changed in /etc/login.defs?
5. Did anything odd get added to root's profile (/root/.profile, I think)?
6. Did you do any update to the system recently that might have introduced 
a library mismatch with su? (I'm not sure which library has the setgid() 
call, but glibc is likely.)

Finally, have you tried a console login and su? If not, you should, to 
detemine if the problem is connected with the remote aspect of the process. 
If it is, you need to provide more detail about it ... telnet, ssh, rsh, or 
what, for example? Might there be restrictions on what the system will 
permit that login method to do? You mention that the system runs nfs and 
samba ... do they play any obvious role in what you are doing (e.g., is 
either relevant home directory an nfs share)?



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2003-12-29 16:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-27  8:20 C Compiler Peter
2003-12-27 10:18 ` Amin
2003-12-27 11:10 ` John Kelly
2003-12-27 17:46 ` caszonyi
2003-12-28  4:21 ` joy
2003-12-29 12:51   ` setgid: Operation not permitted chuck gelm net
2003-12-29 16:26     ` Ray Olszewski [this message]
2003-12-29 18:41       ` chuck gelm net
2003-12-30 18:26         ` Jos Lemmerling
2003-12-30  0:40       ` chuck gelm net
2003-12-29 20:44     ` caszonyi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5.1.0.14.1.20031229081228.01f1b6a8@celine \
    --to=ray@comarre.com \
    --cc=linux-newbie@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox