From owner-freebsd-current@FreeBSD.ORG Tue Nov 11 20:17:57 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EFF2316A for ; Tue, 11 Nov 2014 20:17:57 +0000 (UTC) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BF3557C6 for ; Tue, 11 Nov 2014 20:17:57 +0000 (UTC) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 54645205C0 for ; Tue, 11 Nov 2014 15:08:33 -0500 (EST) Received: from web3 ([10.202.2.213]) by compute4.internal (MEProxy); Tue, 11 Nov 2014 15:08:33 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:x-sasl-enc:from:to:cc :mime-version:content-transfer-encoding:content-type:in-reply-to :references:subject:date; s=smtpout; bh=GNmYyttTk34fBk3aoRqM5Gh5 kyk=; b=mcLryOvIc4r0/alU4Hzeje8g1ir6+MA0glWGLiPbQ3y5zcc5c4QJfUjt Lneebytm0UHS0277J5ZhGiN2i4v5DR6GUGLgkMy54ZJfkbZ9eu4JwSEFzQ0ptg1K sWZK8ncaIClsjPRmjRzHNuLUEp7GPZzypnUPmx11BF5tw0mdaCk= Received: by web3.nyi.internal (Postfix, from userid 99) id 3301910E90A; Tue, 11 Nov 2014 15:08:33 -0500 (EST) Message-Id: <1415736513.1756131.189800941.79451E0C@webmail.messagingengine.com> X-Sasl-Enc: zOYb/QgP24Fn7ip8LiF1U+U67JGaGQqrnxl8uS6GEGwl 1415736513 From: Mark Felder To: Dimitry Andric MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-9183bd94 In-Reply-To: <2C79EC19-7271-4AC1-B9F8-B2992993823A@FreeBSD.org> References: <5460B143.3010004@FreeBSD.org> <1415676518.1517572.189478341.09FB6AE5@webmail.messagingengine.com> <2C79EC19-7271-4AC1-B9F8-B2992993823A@FreeBSD.org> Subject: Re: Changing timezone without reboot/restarting each service? Date: Tue, 11 Nov 2014 14:08:33 -0600 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2014 20:17:58 -0000 On Tue, Nov 11, 2014, at 13:16, Dimitry Andric wrote: > On 11 Nov 2014, at 04:28, Mark Felder wrote: > > > > On Mon, Nov 10, 2014, at 06:36, Lev Serebryakov wrote: > >> > >> After changing timezones in Russia (with replacing /etc/localtime > >> with new file), I found that cron works in "old" timezone till > >> restart. And all other services do the same, but cron is most obvious > >> here :) > >> > >> Looks like libc reads timezone only once and it could not be chamged > >> for process without restart (which leads to, effectivly, restart of > >> whole server). > >> > >> Is it known problem? I think, it should be fixed somehow. I > >> understand, that re-check timezone file on each time-related call > >> could be expensive, though :( > >> > > > > I think this was one of the crowning achievements of systemd, but I'm > > sure someone can come up with something much more sane than that to > > address this problem. > > Actually, it isn't: > http://www.freedesktop.org/wiki/Software/systemd/timedated/ > > This reads "Note that this service will not inform you about system time > changes. Use timerfd() with CLOCK_REALTIME and TFD_TIMER_CANCEL_ON_SET > for that." > > So it mostly looks like a shared service to provide the graphical time > control panel for GNOME. > Aha, I guess the article I read was as reliable as jamming all that code into PID 1. :-)