|
Bugzilla – Full Text Bug Listing |
| Summary: | systemd-nspawn, still errors because /etc/localtime is not a symlink | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.3 | Reporter: | Tony Su <tonysu> |
| Component: | Basesystem | Assignee: | Dirk Mueller <dmueller> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | dmueller, fcrozat, jsuchome, werner |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 12.3 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Tony Su
2013-04-01 15:57:29 UTC
We do support localtime as a symlink but if you upgraded an old system and didn't change timezone, the symlink isn't created. There might still be some issue on yast not creating /etc/localtime as a symlink.. (In reply to comment #1) > We do support localtime as a symlink but if you upgraded an old system and > didn't change timezone, the symlink isn't created. > > There might still be some issue on yast not creating /etc/localtime as a > symlink.. Will take a closer look at this. Yes, the Host system is an upgrade 12.2 (fresh) > 12.3. Yes, /etc/localtime was some kind of encrypted text file. Replaced it with a symlink to /usr/share/zoneinfo/... and seems to be working for the main Host system. Result is no more of the original problem when invoking systemd-nspawn, just some unrelated permissions problem. But, believe the symlink implementation has its own bug, which seems to be widely reported on Fedora... During bootup, observed the following error just before booting into Plymouth... fast TSC calibration failed Seems to be a non-critical error of some sort, ironically the solution seems to be to configure localtime to point to a file instead of as a symlink...:) So, however this issue is to be addressed(or not, should this be addressed upstream or in openSUSE especially if the symbolic link method may be imperfect today?), the problem seems to have been definitely identified. reassigning to YaST team. Guys, could you make yast time&date module to create /etc/localtime as a symlink instead of a hard copy of the timezone file ? (or use timedated D-Bus api if you can to do the heavy lifting). YaST does not create /etc/localtime, at least not directly. Werner, is 'zic' call (done by YaST) reponsible for its creation? Indeed ... Currently we have three patches around tzcode-link.diff, tzcode-symlink.patch, and tzcode-zic.diff ... Now with /usr part of the root file system or mounted within initrd below the root file system, the default should become a symbolic link. That is drop the copy code and make symbolic link to the default and NOT the hard link ... OK maybe timedatectl(1) is able to handle a hard link but I do not know this (guess: it does not). Adding maintainer of Base:System/timezone to carbon copy list and re-assign I can confirm timedatectl doesn't like hardlink and will use /etc/sysconfig/clock in that case :) Why this bug has become assigned to systemd-maintainers? This bug has to be solved in package timezone ... and maybe this one is a duplicate of bnc #845530 /etc/localtime is a symlink now on systemd distros: ------------------------------------------------------------------- Mon Apr 29 20:47:33 UTC 2013 - crrodriguez@opensuse.org - /etc/localtime must be a symlink to /usr/share/zoneinfo/$TIMEZONE so systemd-timedated and its command line tool timedatectl can work correctly. Yast already does the right thing. |