Public bug reported:
This affects Ubuntu Hardy (8.04)
To replicate this bug, set umask in /etc/profile to something *less*
restrictive than the default 022. I'm trying to use 002 in order to have users
create group writeable files in an office collaboration environment. Log out
and in again for
I agree that this bug should have a slightly higher priority: it's also
a regression from previously correct behaviour. We are in an office
environment where collaboration and sharing files over the network are
core to our functioning. Since upgrading from Feisty (7.04), we're
having problems every
My usage scenario: A server contains a directory owned by group
'collab', which is group writeable and has the setgid bit set. This
means that all new directories created underneath it will also be owned
by group 'collab'. The server is set up with accounts for users whose
desktop systems automati
I agree that this bug should have a slightly higher priority: it's also
a regression from previously correct behaviour. We are in an office
environment where collaboration and sharing files over the network are
core to our functioning. Since upgrading from Feisty (7.04), we're
having problems every
My usage scenario: A server contains a directory owned by group
'collab', which is group writeable and has the setgid bit set. This
means that all new directories created underneath it will also be owned
by group 'collab'. The server is set up with accounts for users whose
desktop systems automati
Public bug reported:
This affects Ubuntu Hardy (8.04)
To replicate this bug, set umask in /etc/profile to something *less*
restrictive than the default 022. I'm trying to use 002 in order to have users
create group writeable files in an office collaboration environment. Log out
and in again for
Public bug reported:
This affects Ubuntu Hardy (8.04)
To replicate this bug, set umask in /etc/profile to something *less*
restrictive than the default 022. I'm trying to use 002 in order to have users
create group writeable files in an office collaboration environment. Log out
and in again for
I agree that this bug should have a slightly higher priority: it's also
a regression from previously correct behaviour. We are in an office
environment where collaboration and sharing files over the network are
core to our functioning. Since upgrading from Feisty (7.04), we're
having problems every
My usage scenario: A server contains a directory owned by group
'collab', which is group writeable and has the setgid bit set. This
means that all new directories created underneath it will also be owned
by group 'collab'. The server is set up with accounts for users whose
desktop systems automati
Public bug reported:
This affects Ubuntu Hardy (8.04)
To replicate this bug, set umask in /etc/profile to something *less*
restrictive than the default 022. I'm trying to use 002 in order to have users
create group writeable files in an office collaboration environment. Log out
and in again for
I agree that this bug should have a slightly higher priority: it's also
a regression from previously correct behaviour. We are in an office
environment where collaboration and sharing files over the network are
core to our functioning. Since upgrading from Feisty (7.04), we're
having problems every
My usage scenario: A server contains a directory owned by group
'collab', which is group writeable and has the setgid bit set. This
means that all new directories created underneath it will also be owned
by group 'collab'. The server is set up with accounts for users whose
desktop systems automati
Public bug reported:
This affects Ubuntu Hardy (8.04)
To replicate this bug, set umask in /etc/profile to something *less*
restrictive than the default 022. I'm trying to use 002 in order to have users
create group writeable files in an office collaboration environment. Log out
and in again for
I agree that this bug should have a slightly higher priority: it's also
a regression from previously correct behaviour. We are in an office
environment where collaboration and sharing files over the network are
core to our functioning. Since upgrading from Feisty (7.04), we're
having problems every
My usage scenario: A server contains a directory owned by group
'collab', which is group writeable and has the setgid bit set. This
means that all new directories created underneath it will also be owned
by group 'collab'. The server is set up with accounts for users whose
desktop systems automati
Public bug reported:
This affects Ubuntu Hardy (8.04)
To replicate this bug, set umask in /etc/profile to something *less*
restrictive than the default 022. I'm trying to use 002 in order to have users
create group writeable files in an office collaboration environment. Log out
and in again for
I agree that this bug should have a slightly higher priority: it's also
a regression from previously correct behaviour. We are in an office
environment where collaboration and sharing files over the network are
core to our functioning. Since upgrading from Feisty (7.04), we're
having problems every
My usage scenario: A server contains a directory owned by group
'collab', which is group writeable and has the setgid bit set. This
means that all new directories created underneath it will also be owned
by group 'collab'. The server is set up with accounts for users whose
desktop systems automati
18 matches
Mail list logo
