[systemd-devel] Problems with setting up systemd
Maciej Piechotka
uzytkownik2 at gmail.com
Fri May 20 05:36:19 PDT 2011
On Fri, 2011-05-20 at 14:22 +0200, Lennart Poettering wrote:
> On Fri, 20.05.11 12:56, Maciej Piechotka (uzytkownik2 at gmail.com) wrote:
>
> > # systemctl enable hwclock-load.service
> > Cannot link /lib64/systemd/system/hwclock-load.service
> > to /etc/systemd/system/sysinit.target.wants/hwclock-load.service,
> > symlink exists already and points
> > to /lib/systemd/system/hwclock-load.service.
> >
> > In OpenRC scripts the flag --utc is used. I'll try to add it manually.
>
> Don't!
>
> The right place to configure UTC/LOCAL RTC is in /etc/adjtime, third
> line. See man page of hwclock.
>
Ok - I won't. The file is:
0.000000 1305883630 0.000000
1305883630
UTC
So it looks like the UTC is set - so where could be the problem? Could
hwclock be scheduled after fsck?
> > > If the LVM device above doesn't show up systemd will have to timeout for
> > > 90s.
> > >
> >
> > I think I know where's problem. But could systemd print something about
> > timeout.
>
> It actually does.
>
Hmm. I'm sure it didn't which means:
- There is bug in systemd
- I haven't notice it
- It is something else
> Lennart
>
Regards
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20110520/bfe6cca0/attachment.pgp>
More information about the systemd-devel
mailing list