Re: Setting up sfssd on Linux: Success!, what about dhcp hosts?

> > So I'm guessing that server will only listen to requests for the current
> > hostname, even if the ip is the same.
> > When I try to connect to @<ip>,<id> or even
> > @<dhcp hostname without domain>,<id>, it fails.
> >
> > Is that correct? Can anybody tell me why that is a necessity, and if any
> > workarounds exist? Or in general just shed light on the subject? The
> > documentation doesn't really mention anything.
>
> In general the name that the SFS client has for the server has to
> match the name that the server has for itself.  The SFS server gets
> its name by default from the system hostname.  However, you can
> override this default by setting the environment variable SFS_HOSTNAME
> before running sfssd.  (You can also individually configure sfsrwsd
> and sfsauthd to have a particular hostname by the hostname directive
> in their respective configuration files.)

I just tested this by setting SFS_HOSTNAME to my ip address, and it works.
Is there a reason for this? I would think that anything that resolves to
the correct host would be okay, as long as the public key matches?

If there is a reason, could it please be documented, and if there is no
reason, could it please be fixed? :)

In our organisation, we use cnames a lot for systems, so this makes
implementing sfs just a little bit harder. Or is there a possibility for
one host to serve multiple sfs-hosts? (I'm guessing, only on different
ports)

Thanks!

Wout.