#54196 Shell services issue: newgrp

Ian Bicking

Permissions for the pylogo project seem all funny on
shell.sf.net. For instance:

SF:~$ hostname
SF:~$ echo $USER
SF:~$ groups
users webware cheetahtemplate docutils funformkit
expwebware webware cheetahtemplate docutils funformkit
expwebware sqlobject sqlobject webware-sandbox
webware-sandbox formencode formencode pylogo pylogo
SF:~$ cd /home/groups/p/py/pylogo
SF:/home/groups/p/py/pylogo$ ls -ld htdocs/
drwxrwsr-x 2 dummy pylogo 4096 Nov 4 10:36
SF:/home/groups/p/py/pylogo$ cd htdocs/
SF:/home/groups/p/py/pylogo/htdocs$ echo test > index.html
-bash: index.html: No such file or directory
SF:/home/groups/p/py/pylogo/htdocs$ cp ~/index.html .
cp: cannot create regular file `./index.html':
Permission denied

So, to summarize: I'm part of the pylogo group,
/home/groups/p/py/pylogo is group owned by pylogo and
is group writable, but I can't seem to write to it.
I'm very confused. Other projects I manage don't act
like this. There were several problems with the pylogo
CVS after it was set up, maybe there were other
problems with the setup...? (the pylogo project is a
several days old now, so there shouldn't be any more
changes that need to propogate)



  • David Burley

    David Burley - 2003-11-18
    • milestone: --> Second Level Support
    • assigned_to: nobody --> burley
    • summary: pylogo: permissions in a funk --> Shell services issue: newgrp
    • status: open --> closed
  • David Burley

    David Burley - 2003-11-18

    Logged In: YES


    The SourceForge.net team is currently in the process of
    investigating a similar circumstance for another user. Unix
    group membership is split between primary and supplementary
    groups. The normal count of 'primary' groups is 16, before
    you need to worry about this behavior. The issue at hand is
    that the primary group count is significantly lower than
    expected (8); this is likely a platform default which came
    up as result of our recent
    shell server migration.

    In the interim, you should make use of 'newgrp GROUPNAME' to
    change the group associated with your user account before
    performing commands within the project web space of that
    group. i.e. 'newgrp projectname will change your effective
    group to 'projectname' thus permitting you to write
    within the projectname project group directory space.

    To transfer web content to your project group directory
    space via SCP, you would:

    1. Use scp to transfer the files to your user account home
    directory (/home/users/u/us/username) on

    2. Login via SSH (interactively) to shell.sourceforge.net

    3. Execute 'newgrp projectname'.

    4. Use 'mv' to move the files in question to your project
    group directory.

    This issue is still open, though you have been provided a
    set of instructions which may be used to work around this
    issue. To ensure smooth handling of this issue, all
    requests regarding this particular problem are now being
    consolidated under a master bug report, Support Request 607417.

    Any progress on this issue will now be posted against that
    Support Request. Once this issue has been resolved, notice
    will be posted to the Site Status page (accessible using the
    'Site Status' link in the left navbar).

    If you wish to keep informed as to the progress on this
    issue, please monitor the following support request:

    As part of this issue consolidation, this Support Request
    will now be closed.

    Thank you,

    SourceForge.net support


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks