Re: getgroup invalid argument in /var/adm/messages

From: Ramin Dousti (ramin_at_cannon.eng.us.uu.net)
Date: 07/24/03

  • Next message: Schubert, John [NTWK SVCS]: "RE: getgroup invalid argument in /var/adm/messages"
    Date: Thu, 24 Jul 2003 16:05:43 -0400
    To: djtech@djtech.org
    
    

    I might be wrong but I don't think its a matter of "sshd" belonging to what
    groups. It's the user who is logging into the machine, for whom a forked sshd
    is running, belonging to what groups. (I hope my statement is grammatically
    correct ;-)

    Ramin

    On Thu, Jul 24, 2003 at 03:17:20PM -0400, djtech@djtech.org wrote:

    > Sounds like SSH is doing its job then. To see how many groups sshd is in use
    > this cmd:
    >
    > grep -v ^# /etc/group|grep sshd|wc -l
    >
    > Quoting "Schubert, John [NTWK SVCS]" <jschub01@sprintspectrum.com>:
    >
    > > The only assigned groups I'm aware of are the GID assigned within /etc/group.
    > > I decided to take a look at the server's /etc/group file and was astounded.
    > > Their group file was thousands of lines long, with dozens blank or containing
    > > only a single name for a group. I have a script that we built for rogue
    > > systems which we were taking over sys admin duties that also have a group
    > > file out of control. So I will run this script and see if the nagging alarm
    > > goes away.
    > >
    > > There were so many lines, I couldn't tell you how many groups are in the
    > > file. I would estimate 18-25.
    > >
    > > Thanks..
    > > John
    >


  • Next message: Schubert, John [NTWK SVCS]: "RE: getgroup invalid argument in /var/adm/messages"