Systemd discussion - during the V cycle

[mc4man]

The time here is correct everywhere inc. in system setup & win8, the init doesn't *seem* to matter.
As far as your last command likely hwclock defaults to utc, that shouldn't effect anything (system time
I gather you can switch the hwclock to system time for the session, why or to what (dis)advantage don't know

sudo hwclock -w

[Cavsfan]

The time here is correct everywhere inc. in system setup & win8, the init doesn't *seem* to matter.
As far as your last command likely hwclock defaults to utc, that shouldn't effect anything (system time
I gather you can switch the hwclock to system time for the session, why or to what (dis)advantage don't know

sudo hwclock -w

Booting with all the operating systems (7) I have on this PC the time is correct as long as I boot Utopic and Vivid with upstart.
The only thing that works booting systemd is entering sudo ntpdate ntp.ubuntu.com in terminal. Or probably if I put that cron script back in there but I'm not going to.

I just now booted with systemd into both and the time was off by 4 hours. Somehow the bug I created https://bugs.launchpad.net/ubuntu/+s...x/+bug/1382208
got marked as a duplicate of the one you opened https://bugs.launchpad.net/ubuntu/+s...x/+bug/1377698
But that just involved booting with upstart. The problem remains in systemd.

I deleted the line that marked it as a duplicate with an explanation that the difference is systemd-boot. It must have been marked as a dup by some bot because systemd is in the bug description.

Here is what Vivid just displayed upon booting with systemd:



Even though it says it detected the time was off and fixed it, the time was still 4 hours behind.
So, the bug remains and I'm sticking with upstart until it is fixed.

[zika]

Just a little recap for those (like me) that (even ocasionally) used „text“ switch in kernel boot line in order to stop GUI from being started by default. SystemD provides a nice remedy, at the end. Following https://fedoraproject.org/wiki/SysVi...emd_Cheatsheet I've (once I've found some spare time, weekend, etc.): „text“=„systemd.unit=runlevel3.target“. Not to mention isolate and other switches for systemctl that wor very nicely. Once You start thinking SysteD way it all fits like a glove. Enjoy.
(systemd.unit=emergency.service for recovery boot)

[Cavsfan]

I can confirm that the US Eastern Standard Time problem being 4 hours behind is fixed with today's updates in Vivid.
I had been using upstart since this was a major problem for me. But, when I seen the update I booted into Vivid Gnome systemd for the first time since installing it and the time is correct.
It looks like a lot of work went into this:

systemd (215-6ubuntu1) vivid; urgency=medium

* Merge with Debian unstable. Remaining Ubuntu changes:
- Create disk/by-partlabel links for mmcblk partitions.
- Hack to support system-image read-only /etc, and modify files in
/etc/writable/ instead.
- debian/rules: Drop doc dir symlinking. It creates havoc with dpkg
upgrades, and we already have the automatic per-file symlinking.
- debian/rules: Add an epoch to libgudev.
- Don't install 80-networking.rules and the Debian *.agent scripts, we
never supported them in Ubuntu. Instead, extend systemd's "net" device
udev rule to trigger ifup@.service on network devices.
- Keep our much simpler udev maintainer scripts (all platforms must
support udev, no debconf).
- Add udev Apport package hook.
- debian/extra/initramfs.top: Drop $ROOTDELAY, we do that in a more
sensible way with wait-for-root. Will get applicable to Debian once
Debian gets wait-for-root in initramfs-tools.
- debian/extra/initramfs.bottom: If LVM is installed, settle udev,
otherwise we get missing LV symlinks. Workaround for LP #1185394.
- Add 40-hyperv-hotadd.rules: Workaround for LP #1233466.
- Mark graphics devices as PRIMARY_DEVICE_FOR_DISPLAY so that we can wait
for those in plymouth.
- Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv
dependencies to "lvm2" which is handled with udev rules in Ubuntu.
- Add /run/shm -> /dev/shm symlink in debian/tmpfiles.d/debian.conf
(LP: #1320534, Closes: #674755).
- Lower Breaks: to lvm2 again. Our lvm2 package has always used udev for
device setup, and thus is be compatible with systemd, too.
- Lower Breaks: to plymouth version which has the udev inotify fix in
Ubuntu.
- Add HP ProLiant Server Cartridge power control support.
- Provide shutdown fallback for upstart. (LP: #1370329)
- Add boot-and-services autopkgtest to check booting with systemd-sysv and
that the most crucial services behave as expected.
- debian/ifup@.service: Additionally run for "auto" class. We don't really
support "allow-hotplug" in Ubuntu at the moment, so we need to deal with
"auto" devices appearing after "/etc/init.d/networking start" already
ran. (LP: #1374521)

Upgrade fixes, keep until 16.04 LTS release:
- systemd Conflicts/Replaces/Provides systemd-services.
- Remove obsolete systemd-logind upstart job.

* Clean up obsolete /etc/udev/rules.d/README on upgrades. (LP: #1381655)
* Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In Ubuntu
we currently keep the setting whether the RTC is in local or UTC time
in /etc/default/rcS "UTC=yes|no", instead of /etc/adjtime. (LP: #1377258)
* Add systemd Apport hook for adding systemd-delta and information about
failed units.

-- Martin Pitt <martin.pitt@ubuntu.com> Wed, 19 Nov 2014 08:55:55 +0100

Hopefully this will make it to Trusty soon. I just checked and it has not yet.

[Cavsfan]

I guess I was wrong about Vivid systemd time being fixed. Right now it shows exactly 5 hours ahead.

[zika]

http://anzwix.com/a/systemd/NEWSPrep...SForNewRelease

[cariboo]

Is there a way to keep upstart from re-installing it self automatically, if I forget to check what is being installed, as every time it gets installed, it breaks my system.

[zika]

Is there a way to keep upstart from re-installing it self automatically, if I forget to check what is being installed, as every time it gets installed, it breaks my system.

???
What do You mean by „re-installing“? Do You have systemd-sysv installed? If You do that shoud prevent UpStart from getting even near. You've got my attention.
Behaviour like the one You mention {sh,c}ould happen on Debian, but even there that should be resolved.

[cariboo]

I did have systemd-sysv installed, but with the latest updates, upstart was installed again. This is the second time it happened, the first time the system just ran as it should, but this time both monitors shutdown, and when my Benq restarted, there was only a flashing cursor, and upon reboot, at the login screen, the mouse cursor disappeared after I had logged in.

To get things working again, I started in recovery mode, and installed systemd-sysv again, while I was at it, I removed the nvidia-331 drivers, but I don't think that was a part of the problem.

[zika]

I did have systemd-sysv installed, but with the latest updates, upstart was installed again. This is the second time it happened, the first time the system just ran as it should, but this time both monitors shutdown, and when my Benq restarted, there was only a flashing cursor, and upon reboot, at the login screen, the mouse cursor disappeared after I had logged in.
To get things working again, I started in recovery mode, and installed systemd-sysv again, while I was at it, I removed the nvidia-331 drivers, but I don't think that was a part of the problem.

The only reason I could think of is that by some sort of glitch You do have some dependency issues unresolved. Try to list what packages do You have from UpStart installed. Maybe some atavism still lurkes on Your machine.
It should be:

:~$ dpkg -l|grep upstart
ii  libupstart1:amd64                                     1.13.2-0ubuntu5                                          amd64        Upstart Client Library
ii  upstart-bin                                           1.13.2-0ubuntu5                                          amd64        event-based init daemon - essential binaries

I do not clearly remember if I did cleaning of UpStart manually before it became official.