Why is the output from `groups` different from `groups user` if Im currently logged in as user?
Im not sure why the following have different output. My understanding is that groups without specifying a user give all the groups the currently logged in user is a member of.
jacob@box:~$ groups
jacob adm lp dialout cdrom plugdev lpadmin sambashare
jacob@box:~$ groups jacob
jacob : jacob
Also what does it mean "groups of the current process" (from the groups man page)? Where are they set up?
NOTE: My distro is Ubuntu.
linux ubuntu permissions user-accounts
migrated from stackoverflow.com Jun 8 '11 at 18:07
This question came from our site for professional and enthusiast programmers.
add a comment |
Im not sure why the following have different output. My understanding is that groups without specifying a user give all the groups the currently logged in user is a member of.
jacob@box:~$ groups
jacob adm lp dialout cdrom plugdev lpadmin sambashare
jacob@box:~$ groups jacob
jacob : jacob
Also what does it mean "groups of the current process" (from the groups man page)? Where are they set up?
NOTE: My distro is Ubuntu.
linux ubuntu permissions user-accounts
migrated from stackoverflow.com Jun 8 '11 at 18:07
This question came from our site for professional and enthusiast programmers.
@Jake Try logging out and then back in.
– cnicutar
Jun 8 '11 at 17:58
I am having this issue in reverse. 'groups myname' gives me all the groups I have in the /etc/groups file, but doing just 'groups' shows me only my primary group. And, indeed, commands that require I be in a certain supplementary group fail due to lack of permissions. Sure wish I knew what was causing this.
– Todd Walton
Dec 10 at 20:57
add a comment |
Im not sure why the following have different output. My understanding is that groups without specifying a user give all the groups the currently logged in user is a member of.
jacob@box:~$ groups
jacob adm lp dialout cdrom plugdev lpadmin sambashare
jacob@box:~$ groups jacob
jacob : jacob
Also what does it mean "groups of the current process" (from the groups man page)? Where are they set up?
NOTE: My distro is Ubuntu.
linux ubuntu permissions user-accounts
Im not sure why the following have different output. My understanding is that groups without specifying a user give all the groups the currently logged in user is a member of.
jacob@box:~$ groups
jacob adm lp dialout cdrom plugdev lpadmin sambashare
jacob@box:~$ groups jacob
jacob : jacob
Also what does it mean "groups of the current process" (from the groups man page)? Where are they set up?
NOTE: My distro is Ubuntu.
linux ubuntu permissions user-accounts
linux ubuntu permissions user-accounts
edited Jul 23 at 9:11
slm
6,16563846
6,16563846
asked Jun 8 '11 at 17:37
Jake
38438
38438
migrated from stackoverflow.com Jun 8 '11 at 18:07
This question came from our site for professional and enthusiast programmers.
migrated from stackoverflow.com Jun 8 '11 at 18:07
This question came from our site for professional and enthusiast programmers.
@Jake Try logging out and then back in.
– cnicutar
Jun 8 '11 at 17:58
I am having this issue in reverse. 'groups myname' gives me all the groups I have in the /etc/groups file, but doing just 'groups' shows me only my primary group. And, indeed, commands that require I be in a certain supplementary group fail due to lack of permissions. Sure wish I knew what was causing this.
– Todd Walton
Dec 10 at 20:57
add a comment |
@Jake Try logging out and then back in.
– cnicutar
Jun 8 '11 at 17:58
I am having this issue in reverse. 'groups myname' gives me all the groups I have in the /etc/groups file, but doing just 'groups' shows me only my primary group. And, indeed, commands that require I be in a certain supplementary group fail due to lack of permissions. Sure wish I knew what was causing this.
– Todd Walton
Dec 10 at 20:57
@Jake Try logging out and then back in.
– cnicutar
Jun 8 '11 at 17:58
@Jake Try logging out and then back in.
– cnicutar
Jun 8 '11 at 17:58
I am having this issue in reverse. 'groups myname' gives me all the groups I have in the /etc/groups file, but doing just 'groups' shows me only my primary group. And, indeed, commands that require I be in a certain supplementary group fail due to lack of permissions. Sure wish I knew what was causing this.
– Todd Walton
Dec 10 at 20:57
I am having this issue in reverse. 'groups myname' gives me all the groups I have in the /etc/groups file, but doing just 'groups' shows me only my primary group. And, indeed, commands that require I be in a certain supplementary group fail due to lack of permissions. Sure wish I knew what was causing this.
– Todd Walton
Dec 10 at 20:57
add a comment |
3 Answers
3
active
oldest
votes
It could be one of the following:
- It could be a bug (although I doubt it)
- You may need to logout and login again
The groups are set in the /etc/group
.
add a comment |
Just as every process has a current real and effective user ID, and a real and effective group ID, it also has a list of supplementary groups. These are numbers (not names) all maintained by the kernel. They are set by the login process (or display manager) when you log it, just like your user ID. They are inherited by sub-processes, just like your user ID.
When you run groups
with no arguments, it ultimately invokes getgroups() to obtain the supplementary group list from the kernel. (On my Linux system, /usr/bin/groups is a shell script that runs "id -Gn", which in turn invokes getgroups().)
When you run groups username
, the command has to "guess" what the supplementary groups will be when that user logs in. It generally does this by reading /etc/group or talking to NIS or talking to nscd or... Well, there are a lot of ways it might work.
What you are observing is similar to discovering that your current real user ID and your entry in /etc/passwd are inconsistent. This means there is something a little odd about your system's configuration, but it is hard to say what without more investigation.
add a comment |
(Remark: The groups
command, although still useful, is mostly superseded by
the id command.)
A user has a primary group that is traditionally defined in the file
/etc/passwd
file with which he logs in, but that today may have other sources.
He may also be a member of additional groups, known as secondary or
supplementary groups,
traditionally specified in the file /etc/groups
,
but which today can also come from or be implied by
additional sources (such as NIS, LDAP, SAMBA etc).
Primary and supplementary groups are defined at the time of login and remain current.
However, the user can at any time change his current active primary group
by using the newgrp
command.
The login process sets the primary and supplementary groups.
For the later, it typically calls the libc function
initgroups,
which compiles the list of supplementary group data and passes it to the
setgroups function,
which establishes it in the context of the process.
The sources of information for initgroups
are:
/etc/passwd for the primary login
/etc/groups
for supplementary groups
/etc/nsswitch.conf
for sources to supplementary groups, which is described as:
used by the GNU C Library and certain other applications to
determine the sources from which to obtain name-service information
in a range of categories, and in what order. Each category of
information is identified by a database name.
The groups
command shows the groups as currently applied to your user,
and the list will start with the current primary group followed by the
supplementary groups from the time of login.
Any changes to the sources of the data from after the time of login
are not reflected in the displayed list.
The groups username
command is asking Linux to calculate the groups for that user,
which it will do using principally the files /etc/password
and /etc/groups
and then the additional sources.
This will reflect the current situation of the system files and may not
equal the current groups that are still in effect from the time of login.
The groups username
command may give a different result
when it doesn't use all the sources that the login process used to calculate
your supplementary groups, which is what apparently happened in your case.
These sources may not be accessible from your login or may just not be consulted
by the command.
Using the id username
command may give better results, although also not guaranteed
to be as complete as that of the login process. The id
command
is more recent than, and was intended to be more precise than,
the old groups
command.
While the groups
command gives a precise and correct result,
you have well demonstrated that the groups username
command
cannot be depended upon to do the same.
Without examining the source-code of the groups
command, I would guess
that the implementation of the groups username
command in your Linux
distribution analyzes /etc/groups
, which in your case contained nothing,
but does not use /etc/nsswitch.conf
, from which came all of your
supplementary groups. Therefore is listed only the primary group name,
jacob
.
For more information see:
credentials(7) - Linux man page- How to use nsswitch.conf to find Linux system information
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f294650%2fwhy-is-the-output-from-groups-different-from-groups-user-if-im-currently-log%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
It could be one of the following:
- It could be a bug (although I doubt it)
- You may need to logout and login again
The groups are set in the /etc/group
.
add a comment |
It could be one of the following:
- It could be a bug (although I doubt it)
- You may need to logout and login again
The groups are set in the /etc/group
.
add a comment |
It could be one of the following:
- It could be a bug (although I doubt it)
- You may need to logout and login again
The groups are set in the /etc/group
.
It could be one of the following:
- It could be a bug (although I doubt it)
- You may need to logout and login again
The groups are set in the /etc/group
.
answered Jun 8 '11 at 17:43
cnicutar
add a comment |
add a comment |
Just as every process has a current real and effective user ID, and a real and effective group ID, it also has a list of supplementary groups. These are numbers (not names) all maintained by the kernel. They are set by the login process (or display manager) when you log it, just like your user ID. They are inherited by sub-processes, just like your user ID.
When you run groups
with no arguments, it ultimately invokes getgroups() to obtain the supplementary group list from the kernel. (On my Linux system, /usr/bin/groups is a shell script that runs "id -Gn", which in turn invokes getgroups().)
When you run groups username
, the command has to "guess" what the supplementary groups will be when that user logs in. It generally does this by reading /etc/group or talking to NIS or talking to nscd or... Well, there are a lot of ways it might work.
What you are observing is similar to discovering that your current real user ID and your entry in /etc/passwd are inconsistent. This means there is something a little odd about your system's configuration, but it is hard to say what without more investigation.
add a comment |
Just as every process has a current real and effective user ID, and a real and effective group ID, it also has a list of supplementary groups. These are numbers (not names) all maintained by the kernel. They are set by the login process (or display manager) when you log it, just like your user ID. They are inherited by sub-processes, just like your user ID.
When you run groups
with no arguments, it ultimately invokes getgroups() to obtain the supplementary group list from the kernel. (On my Linux system, /usr/bin/groups is a shell script that runs "id -Gn", which in turn invokes getgroups().)
When you run groups username
, the command has to "guess" what the supplementary groups will be when that user logs in. It generally does this by reading /etc/group or talking to NIS or talking to nscd or... Well, there are a lot of ways it might work.
What you are observing is similar to discovering that your current real user ID and your entry in /etc/passwd are inconsistent. This means there is something a little odd about your system's configuration, but it is hard to say what without more investigation.
add a comment |
Just as every process has a current real and effective user ID, and a real and effective group ID, it also has a list of supplementary groups. These are numbers (not names) all maintained by the kernel. They are set by the login process (or display manager) when you log it, just like your user ID. They are inherited by sub-processes, just like your user ID.
When you run groups
with no arguments, it ultimately invokes getgroups() to obtain the supplementary group list from the kernel. (On my Linux system, /usr/bin/groups is a shell script that runs "id -Gn", which in turn invokes getgroups().)
When you run groups username
, the command has to "guess" what the supplementary groups will be when that user logs in. It generally does this by reading /etc/group or talking to NIS or talking to nscd or... Well, there are a lot of ways it might work.
What you are observing is similar to discovering that your current real user ID and your entry in /etc/passwd are inconsistent. This means there is something a little odd about your system's configuration, but it is hard to say what without more investigation.
Just as every process has a current real and effective user ID, and a real and effective group ID, it also has a list of supplementary groups. These are numbers (not names) all maintained by the kernel. They are set by the login process (or display manager) when you log it, just like your user ID. They are inherited by sub-processes, just like your user ID.
When you run groups
with no arguments, it ultimately invokes getgroups() to obtain the supplementary group list from the kernel. (On my Linux system, /usr/bin/groups is a shell script that runs "id -Gn", which in turn invokes getgroups().)
When you run groups username
, the command has to "guess" what the supplementary groups will be when that user logs in. It generally does this by reading /etc/group or talking to NIS or talking to nscd or... Well, there are a lot of ways it might work.
What you are observing is similar to discovering that your current real user ID and your entry in /etc/passwd are inconsistent. This means there is something a little odd about your system's configuration, but it is hard to say what without more investigation.
edited May 22 '14 at 18:28
answered Jun 8 '11 at 17:54
Nemo
25716
25716
add a comment |
add a comment |
(Remark: The groups
command, although still useful, is mostly superseded by
the id command.)
A user has a primary group that is traditionally defined in the file
/etc/passwd
file with which he logs in, but that today may have other sources.
He may also be a member of additional groups, known as secondary or
supplementary groups,
traditionally specified in the file /etc/groups
,
but which today can also come from or be implied by
additional sources (such as NIS, LDAP, SAMBA etc).
Primary and supplementary groups are defined at the time of login and remain current.
However, the user can at any time change his current active primary group
by using the newgrp
command.
The login process sets the primary and supplementary groups.
For the later, it typically calls the libc function
initgroups,
which compiles the list of supplementary group data and passes it to the
setgroups function,
which establishes it in the context of the process.
The sources of information for initgroups
are:
/etc/passwd for the primary login
/etc/groups
for supplementary groups
/etc/nsswitch.conf
for sources to supplementary groups, which is described as:
used by the GNU C Library and certain other applications to
determine the sources from which to obtain name-service information
in a range of categories, and in what order. Each category of
information is identified by a database name.
The groups
command shows the groups as currently applied to your user,
and the list will start with the current primary group followed by the
supplementary groups from the time of login.
Any changes to the sources of the data from after the time of login
are not reflected in the displayed list.
The groups username
command is asking Linux to calculate the groups for that user,
which it will do using principally the files /etc/password
and /etc/groups
and then the additional sources.
This will reflect the current situation of the system files and may not
equal the current groups that are still in effect from the time of login.
The groups username
command may give a different result
when it doesn't use all the sources that the login process used to calculate
your supplementary groups, which is what apparently happened in your case.
These sources may not be accessible from your login or may just not be consulted
by the command.
Using the id username
command may give better results, although also not guaranteed
to be as complete as that of the login process. The id
command
is more recent than, and was intended to be more precise than,
the old groups
command.
While the groups
command gives a precise and correct result,
you have well demonstrated that the groups username
command
cannot be depended upon to do the same.
Without examining the source-code of the groups
command, I would guess
that the implementation of the groups username
command in your Linux
distribution analyzes /etc/groups
, which in your case contained nothing,
but does not use /etc/nsswitch.conf
, from which came all of your
supplementary groups. Therefore is listed only the primary group name,
jacob
.
For more information see:
credentials(7) - Linux man page- How to use nsswitch.conf to find Linux system information
add a comment |
(Remark: The groups
command, although still useful, is mostly superseded by
the id command.)
A user has a primary group that is traditionally defined in the file
/etc/passwd
file with which he logs in, but that today may have other sources.
He may also be a member of additional groups, known as secondary or
supplementary groups,
traditionally specified in the file /etc/groups
,
but which today can also come from or be implied by
additional sources (such as NIS, LDAP, SAMBA etc).
Primary and supplementary groups are defined at the time of login and remain current.
However, the user can at any time change his current active primary group
by using the newgrp
command.
The login process sets the primary and supplementary groups.
For the later, it typically calls the libc function
initgroups,
which compiles the list of supplementary group data and passes it to the
setgroups function,
which establishes it in the context of the process.
The sources of information for initgroups
are:
/etc/passwd for the primary login
/etc/groups
for supplementary groups
/etc/nsswitch.conf
for sources to supplementary groups, which is described as:
used by the GNU C Library and certain other applications to
determine the sources from which to obtain name-service information
in a range of categories, and in what order. Each category of
information is identified by a database name.
The groups
command shows the groups as currently applied to your user,
and the list will start with the current primary group followed by the
supplementary groups from the time of login.
Any changes to the sources of the data from after the time of login
are not reflected in the displayed list.
The groups username
command is asking Linux to calculate the groups for that user,
which it will do using principally the files /etc/password
and /etc/groups
and then the additional sources.
This will reflect the current situation of the system files and may not
equal the current groups that are still in effect from the time of login.
The groups username
command may give a different result
when it doesn't use all the sources that the login process used to calculate
your supplementary groups, which is what apparently happened in your case.
These sources may not be accessible from your login or may just not be consulted
by the command.
Using the id username
command may give better results, although also not guaranteed
to be as complete as that of the login process. The id
command
is more recent than, and was intended to be more precise than,
the old groups
command.
While the groups
command gives a precise and correct result,
you have well demonstrated that the groups username
command
cannot be depended upon to do the same.
Without examining the source-code of the groups
command, I would guess
that the implementation of the groups username
command in your Linux
distribution analyzes /etc/groups
, which in your case contained nothing,
but does not use /etc/nsswitch.conf
, from which came all of your
supplementary groups. Therefore is listed only the primary group name,
jacob
.
For more information see:
credentials(7) - Linux man page- How to use nsswitch.conf to find Linux system information
add a comment |
(Remark: The groups
command, although still useful, is mostly superseded by
the id command.)
A user has a primary group that is traditionally defined in the file
/etc/passwd
file with which he logs in, but that today may have other sources.
He may also be a member of additional groups, known as secondary or
supplementary groups,
traditionally specified in the file /etc/groups
,
but which today can also come from or be implied by
additional sources (such as NIS, LDAP, SAMBA etc).
Primary and supplementary groups are defined at the time of login and remain current.
However, the user can at any time change his current active primary group
by using the newgrp
command.
The login process sets the primary and supplementary groups.
For the later, it typically calls the libc function
initgroups,
which compiles the list of supplementary group data and passes it to the
setgroups function,
which establishes it in the context of the process.
The sources of information for initgroups
are:
/etc/passwd for the primary login
/etc/groups
for supplementary groups
/etc/nsswitch.conf
for sources to supplementary groups, which is described as:
used by the GNU C Library and certain other applications to
determine the sources from which to obtain name-service information
in a range of categories, and in what order. Each category of
information is identified by a database name.
The groups
command shows the groups as currently applied to your user,
and the list will start with the current primary group followed by the
supplementary groups from the time of login.
Any changes to the sources of the data from after the time of login
are not reflected in the displayed list.
The groups username
command is asking Linux to calculate the groups for that user,
which it will do using principally the files /etc/password
and /etc/groups
and then the additional sources.
This will reflect the current situation of the system files and may not
equal the current groups that are still in effect from the time of login.
The groups username
command may give a different result
when it doesn't use all the sources that the login process used to calculate
your supplementary groups, which is what apparently happened in your case.
These sources may not be accessible from your login or may just not be consulted
by the command.
Using the id username
command may give better results, although also not guaranteed
to be as complete as that of the login process. The id
command
is more recent than, and was intended to be more precise than,
the old groups
command.
While the groups
command gives a precise and correct result,
you have well demonstrated that the groups username
command
cannot be depended upon to do the same.
Without examining the source-code of the groups
command, I would guess
that the implementation of the groups username
command in your Linux
distribution analyzes /etc/groups
, which in your case contained nothing,
but does not use /etc/nsswitch.conf
, from which came all of your
supplementary groups. Therefore is listed only the primary group name,
jacob
.
For more information see:
credentials(7) - Linux man page- How to use nsswitch.conf to find Linux system information
(Remark: The groups
command, although still useful, is mostly superseded by
the id command.)
A user has a primary group that is traditionally defined in the file
/etc/passwd
file with which he logs in, but that today may have other sources.
He may also be a member of additional groups, known as secondary or
supplementary groups,
traditionally specified in the file /etc/groups
,
but which today can also come from or be implied by
additional sources (such as NIS, LDAP, SAMBA etc).
Primary and supplementary groups are defined at the time of login and remain current.
However, the user can at any time change his current active primary group
by using the newgrp
command.
The login process sets the primary and supplementary groups.
For the later, it typically calls the libc function
initgroups,
which compiles the list of supplementary group data and passes it to the
setgroups function,
which establishes it in the context of the process.
The sources of information for initgroups
are:
/etc/passwd for the primary login
/etc/groups
for supplementary groups
/etc/nsswitch.conf
for sources to supplementary groups, which is described as:
used by the GNU C Library and certain other applications to
determine the sources from which to obtain name-service information
in a range of categories, and in what order. Each category of
information is identified by a database name.
The groups
command shows the groups as currently applied to your user,
and the list will start with the current primary group followed by the
supplementary groups from the time of login.
Any changes to the sources of the data from after the time of login
are not reflected in the displayed list.
The groups username
command is asking Linux to calculate the groups for that user,
which it will do using principally the files /etc/password
and /etc/groups
and then the additional sources.
This will reflect the current situation of the system files and may not
equal the current groups that are still in effect from the time of login.
The groups username
command may give a different result
when it doesn't use all the sources that the login process used to calculate
your supplementary groups, which is what apparently happened in your case.
These sources may not be accessible from your login or may just not be consulted
by the command.
Using the id username
command may give better results, although also not guaranteed
to be as complete as that of the login process. The id
command
is more recent than, and was intended to be more precise than,
the old groups
command.
While the groups
command gives a precise and correct result,
you have well demonstrated that the groups username
command
cannot be depended upon to do the same.
Without examining the source-code of the groups
command, I would guess
that the implementation of the groups username
command in your Linux
distribution analyzes /etc/groups
, which in your case contained nothing,
but does not use /etc/nsswitch.conf
, from which came all of your
supplementary groups. Therefore is listed only the primary group name,
jacob
.
For more information see:
credentials(7) - Linux man page- How to use nsswitch.conf to find Linux system information
edited Dec 11 at 9:33
answered Dec 10 at 22:31
harrymc
253k12259562
253k12259562
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f294650%2fwhy-is-the-output-from-groups-different-from-groups-user-if-im-currently-log%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
@Jake Try logging out and then back in.
– cnicutar
Jun 8 '11 at 17:58
I am having this issue in reverse. 'groups myname' gives me all the groups I have in the /etc/groups file, but doing just 'groups' shows me only my primary group. And, indeed, commands that require I be in a certain supplementary group fail due to lack of permissions. Sure wish I knew what was causing this.
– Todd Walton
Dec 10 at 20:57