LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 08-21-2009, 01:09 PM   #1
larryhaja
Member
 
Registered: Jul 2008
Distribution: Slackware 13.1
Posts: 292

Rep: Reputation: 75
I get "Warning: add_groups: Invalid Argument" after logging in.


I am currently running wicd 1.6.2 on Slackware 12.2 using a slightly modified version of wicd.SlackBuild from Slackware -current. Only modification I made was txz to tgz. I know that I had to add myself to the netdev group to get wicd to work as it did before. Although, now when I log in I get this error.
Code:
Warning: add_groups: Invalid Argument
I've had this warning error message before but it was removed when I removed the user from the appropriate group. Just to verify I deleted my user from the netdev group and then re-logged in and the warning message went away. Adding my user back to that group made the warning come back. Any ideas how to to get rid of this warning message?

I did a quick google search and came upon this old forum post.
http://www.linuxquestions.org/questi...gument-426383/
It just reaffirmed what I had already verified.
 
Old 08-21-2009, 07:02 PM   #2
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,553

Rep: Reputation: 422Reputation: 422Reputation: 422Reputation: 422Reputation: 422
probably because netdev is not listed on your /etc/group since you are still running 12.2
 
Old 08-21-2009, 07:31 PM   #3
larryhaja
Member
 
Registered: Jul 2008
Distribution: Slackware 13.1
Posts: 292

Original Poster
Rep: Reputation: 75
Quote:
Originally Posted by willysr View Post
probably because netdev is not listed on your /etc/group since you are still running 12.2
I checked before I added my user to the group. It is listed in /etc/group.
 
Old 08-25-2009, 03:21 PM   #4
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,913

Rep: Reputation: Disabled
I've seen this before, but I simply cannot remember what was causing it and how I made it go away :/
Does "shadowconfig on" as root throw any errors at you?
 
Old 08-25-2009, 06:04 PM   #5
larryhaja
Member
 
Registered: Jul 2008
Distribution: Slackware 13.1
Posts: 292

Original Poster
Rep: Reputation: 75
Quote:
Originally Posted by rworkman View Post
Does "shadowconfig on" as root throw any errors at you?
Here is what I get when I run "shadowconfig on".
Code:
# shadowconfig on
Shadow passwords are now on.
So no errors when the command is issued. Unfortunately, only removing the user from the group prevents the error from happening.
 
Old 08-25-2009, 10:13 PM   #6
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,913

Rep: Reputation: Disabled
Poke me on IRC via private msg, and if we can figure out the solution, we'll post it here. I've got a few ideas, but it will be easier to try them on IRC :-)
 
Old 08-30-2009, 11:57 AM   #7
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,913

Rep: Reputation: Disabled
Someone else ran across this and sent their /etc/group file to me, and while I don't have a solution (yet?), I think I know what's causing it. Count up the groups to which you're adding the relevant user, and I suspect that it will be >16. It seems that 2^4 is the largest number of groups to which any specific user can be added to by login. :/
 
Old 08-30-2009, 12:38 PM   #8
larryhaja
Member
 
Registered: Jul 2008
Distribution: Slackware 13.1
Posts: 292

Original Poster
Rep: Reputation: 75
That's good to know for future reference. Unfortunately, I've already wiped my system clean and installed Slackware 13.0. So, I can't test this out. It seems plausible as my previous user belonged to a lot of groups.

Now I just need to figure out why plasma sometimes eats up a lot of cpu cycles and freezes the panel.
 
Old 08-30-2009, 01:29 PM   #9
Woodsman
Senior Member
 
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482

Rep: Reputation: 534Reputation: 534Reputation: 534Reputation: 534Reputation: 534Reputation: 534
Quote:
Count up the groups to which you're adding the relevant user, and I suspect that it will be >16.
I'll confirm the problem and conjecture. Recently I tried to create a new group called mediausers, which would provide appropriate permissions for handling media files on my new HTPC. I received the same error message all the time. When I removed my normal user from the new group then the error message stopped. My normal account is a member of 16 groups.

A while back when testing Currrent I experienced the same problem with adding root to additional groups. Yup, root is a member of 16 groups.

The error seems harmless but like many error messages, is irritating.

Quote:
It seems that 2^4 is the largest number of groups to which any specific user can be added to by login.
What a silly idea!

Any possibility to patch the source code?
 
Old 08-30-2009, 02:32 PM   #10
faefae
LQ Newbie
 
Registered: Jul 2009
Posts: 3

Rep: Reputation: 0
Quote:
Originally Posted by rworkman View Post
Someone else ran across this and sent their /etc/group file to me, and while I don't have a solution (yet?), I think I know what's causing it. Count up the groups to which you're adding the relevant user, and I suspect that it will be >16. It seems that 2^4 is the largest number of groups to which any specific user can be added to by login. :/
Yes, I will confirm this issue too. My root account has same message after logging (in my case, user root is a member of 18 groups )

Sorry, for my bad english
 
Old 08-30-2009, 11:20 PM   #11
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,913

Rep: Reputation: Disabled
Small update:
1. It seems that this warning is harmless - I put root in eighteen groups, then logged in on the console, got the warning, but root is correctly placed in all eighteen groups.
2. In shadow's source directory, ./libmisc/newgrps.c has a loop starting with "i = 16" -- if you change that to "32" instead and rebuild, the warning goes away. Note that I am NOT recommending that change, especially since the warning seems harmless, because I don't know what other ramifications it might have.
 
Old 08-31-2009, 12:25 AM   #12
Woodsman
Senior Member
 
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482

Rep: Reputation: 534Reputation: 534Reputation: 534Reputation: 534Reputation: 534Reputation: 534
Quote:
if you change that to "32" instead and rebuild, the warning goes away. Note that I am NOT recommending that change, especially since the warning seems harmless, because I don't know what other ramifications it might have.
Checking around the web seems to reveal that NFS is the culprit for the 16 group limit. However, there might be a patch available. This stuff is over my head and makes my eyes water.
 
Old 09-11-2009, 04:11 PM   #13
Gustav 4
LQ Newbie
 
Registered: Jul 2009
Location: Copenhagen, Denmark
Distribution: Fedora 15, Gnome 3
Posts: 12

Rep: Reputation: 0
Hi! I was also getting this warning at login. As advised from this thread, I shaved off a couple of groups from my user account, and that brought down the total number of groups I want attached to my account to 14. The warning disappeared at the subsequent logins. But I was wondering if the warning actually is harmless, and that all listed groups that need to be added to a user account is executed, or if only the first 16 list groups are added?
 
Old 09-12-2009, 04:18 AM   #14
bassmadrigal
Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 211

Rep: Reputation: 41
Quote:
Originally Posted by rworkman View Post
Small update:
1. It seems that this warning is harmless - I put root in eighteen groups, then logged in on the console, got the warning, but root is correctly placed in all eighteen groups.
2. In shadow's source directory, ./libmisc/newgrps.c has a loop starting with "i = 16" -- if you change that to "32" instead and rebuild, the warning goes away. Note that I am NOT recommending that change, especially since the warning seems harmless, because I don't know what other ramifications it might have.
As mentioned a couple of posts above you. As far as we know it is harmless.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] "WARNING: Re-reading the partition table failed with error 22: Invalid argument." ytd Linux - Newbie 6 01-26-2010 10:06 AM
Warning: add_groups: Invalid argument Lufbery Slackware 6 08-30-2009 11:57 AM
error: Error for wireless request "Set Mode" (8B06) : invalid argument "roaming" penguin chick Linux - Wireless Networking 5 08-22-2008 01:16 PM
"cp -p" fails with "cp: setting permissions for `/home/svbld/t': Invalid argument" mkhesin Red Hat 1 02-28-2007 12:57 AM
"Warning: add_groups: Invalid Argument" helliax Linux - General 3 03-20-2006 06:52 AM


All times are GMT -5. The time now is 05:19 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration