Alexei Sheplyakov <[EMAIL PROTECTED]> writes:
> Package: openafs-fileserver
> Version: 1.4.2-4
> Severity: normal
> There are at least two reasons of that.
> 1) fileserver fails to [re-]create the /etc/openafs/server-local/sysid
> file. It would be nice if fileserver refused to start in such a
> situation (it seems to fail in a obscure fashion later anyway) and/or
> print some prominent warning (something like "failed to create sysid
> file, expect random failures").
> BTW I wonder if /etc is a proper location for sysid file. FHS [1] says
> "The /etc hierarchy contains configuration files. A "configuration file"
> is a local file used to control the operation of a program; it must be
> static and cannot be an executable binary"
> The sysid file is not a configuration file (according to the AFS
> administratior guide it is not supposed to be modified manually)
> and it is not static, so I think something like /var/lib/openafs
> would be more appropriate location.
> 2) Salvager fails to create lock files in /etc/openafs/server-local
> (SALVAGE.fs and salvage.lock) and exits without any error messages.
> First of all, some error message would be nice. Secondly, I don't think
> /etc is a proper location for lock files.
> [1] http://www.pathname.com/fhs/pub/fhs-2.3.html
All of /etc/openafs/server-local should probably move to /var. I don't
see anything in there that's really a configuration file in a strict
sense, and indeed OpenAFS wants to modify those files during startup.
Thanks for the report. This is a somewhat risky change and I don't think
it's RC for etch, so I'll take a look at this after etch releases. I'll
see if I can do something about the error handling as well, while I'm at
it.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
