On Tue, Feb 20, 2018 at 06:04:47PM +0100, Lennart Poettering wrote: > On Di, 20.02.18 11:14, Iain Lane ([email protected]) wrote: > > I'm not sure, though, what the best way to specify this in a timer unit > > would be. Perhaps either a new timezone specification "local", or a > > boolean flag UpdateWithTimezoneChange. "local" would act like you > > specified the current timezone, but we would go away and recalculate > > the time on a timezone change. > > If you don't specify a timezone in timer expression you actually > reference the local time. The only issue is that we don't recognize > timezone changes...
That's right. This is the intended behaviour though, so I'm proposing a way to opt into something different. My feeling is that "local" is a confusing name, but we could hash that out at a later stage. > Could you file an RFE issue about this on github? Yep. I filed #8233 now. Let's carry on there. Cheers, -- Iain Lane [ [email protected] ] Debian Developer [ [email protected] ] Ubuntu Developer [ [email protected] ]
signature.asc
Description: PGP signature
_______________________________________________ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
