On Mon, Sep 17, 2007 at 04:23:41PM +0200, Frans Pop wrote: > > But yes, nothing guarantees the creation of the file, so it's best if the > > pam packages take responsibility for this on install.
> Why not just ignore if it does not exist? Seems silly to have an empty file. Because from an upstream standpoint, configuring pam_env to read a non-existent file is a configuration error and should not be ignored silently. It is ignored for purposes of the module's operation, but an error is still logged about the problem. > OTOH, it _is_ the canonical location for system-wide defaults, so maybe a > placeholder file should be created with some suitable comments about its > usage. Yes. > However, I doubt that pam should do this. Seems more like something for > base-files, especially as I don't think we want to make it a conffile. Er, no. /etc/environment is a config file for pam_env and is owned by PAM; there's no reason at all for base-files to be involved. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
