#454 Homes name must contain username

open
nobody
None
1
2015-05-23
2012-09-07
Benn Linger
No

I can use the "home name" directive to change the name of the user's home share, but if it doesn't contain the %u variable, the directive is ignored. I end up finding this in the syslog:

Sep 6 21:02:19 ip-10-8-0-215 afpd[1265]: home name must contain $u.

Note that the inability to have the same name for all users' home shares (e.g. "Backups") breaks Bonjour discovery of Time Machine shares. The name of the share to connect to must be part of the service advertisement (reference), so it can't be different for every user.

Bonjour discovery isn't a huge deal for initial configuration, but it's a huge help if you ever need to restore a system completely (rather than individual files). Without it, you have to use Terminal to mount the AFP share beforehand from the boot CD (or recovery partition) environment, which is unpleasant.

This is something that was possible pre-3.0.

Discussion

  • Benn Linger

    Benn Linger - 2012-09-07

    I've worked around this for now by having a single directory for all users with permissions set such that they can't modify or look into each other's backups, but this seems like something more easily solved through using home directories.

     
  •  HAT

    HAT - 2012-09-10

    It's spec, not bug.

    If name of home volume is "Backups", CNID directory is /var/netatalk/CNID/Backups/ .
    One CNID directory manage all home volumes. This is a problem.

    The current netatalk 3 has similar problem about macro. This is a future subject.

     
  • AxeL

    AxeL - 2015-02-09

    Is there a reason why the home name must contain the username ($u)?

     
  • S. Wyatt Young

    S. Wyatt Young - 2015-05-23

    Any chance we could get this changed, at least to require either $f OR $u in the home name?

     

Log in to post a comment.

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

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks