On Tuesday, March 18, 2008 at 1:53:11 +0100, Karel Zak wrote: > Where do you want to define the $ADJTIME_PATH? /etc/profile? ;-) /etc/profile is maybe not the best place, because it is not above the bootup and shutdown scripts, main callers of hwclock. I would suggest a more upstream place, like /etc/initscript or such. Or a main config /etc/default/hwclock.sh sourced by /etc/profile and by boot scripts. Or whatever else: really distributors and sysadmins are free to do as they prefer. Even define the var only in scripts and root's env, or only in a wrapper. A private /etc/hwclock.conf would cover as much hwclock calls as $ADJTIME_PATH, and have less public exposure. But it is a quite heavy solution. While the env var solution is extra light. In any case --adjfile seems disqualified, at least as the sole method. And there is probably no urgency to implement several methods for such a marginal usage. Alain. -- To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
