Survey on systemd Who uses it?

[piper]

I think a lot of customizations will be lost

I don't think /lib/lsb/init-functions would be editable anymore, I am sure there is a lot more that you won't be able to customize to "your" liking.

How is this going to effect the build process of siduction ?

[dibl]

Are tools provided to read these binary system logs whenever debugging some issue or in looking for errors to document in some bug report?

Yes, the command "systemd-journalctl" is the tool for listing the journal into a "most" window.  I haven't learned the options yet, but the basic command works as advertised.

"man systemd-journalctl" looks very complete.

[timc]

Please note: My objections to systemd have nothing to do with the technical merits of either systemd or sysvinit.

Tim

[bluelupo]

Here is a article from the Debian-Wiki: http://wiki.debian.org/systemd

[DeepDayze]

Are tools provided to read these binary system logs whenever debugging some issue or in looking for errors to document in some bug report?

Yes, the command "systemd-journalctl" is the tool for listing the journal into a "most" window.  I haven't learned the options yet, but the basic command works as advertised.

"man systemd-journalctl" looks very complete.

Great, thanks. Also it might be useful to write a script akin to siduction-paste to highlight things of interest in the systemd logs and put them into a pastebin as part of troubleshooting or bug reporting

[devil]

You can either look at man journalctl or read on it at: http://www.dsm.fordham.edu/cgi-bin/man-cgi.pl?topic=journalctl&ampsect=1v or read Lennarts blog about it on http://0pointer.de/blog/projects/journalctl.html

greetz
devil

[dibl]

I have a laptop that I use mainly for experiments -- why it is still running I don't know.  :mrgreen:   It only took 5 minutes to install systemd, since I am already so experienced.  This one runs on an SSD, and it was already booting up pretty fast, but I was amazed at the boot on systemd -- between 9 and 10 seconds from grub to kdm, and  I have done nothing special to tweak it.

Don't forget to install the libpam-systemd and systemd-sysv packages, and to put systemd-sysv on hold. Here's the hardware:

Code Select Expand

System:    Host: delle6500 Kernel: 3.9-4.towo-siduction-amd64 x86_64 (64 bit)
          Desktop: KDE 4.10.3 Distro: siduction 12.1-RC1 Desperado - kde - (201205152133)
Machine:   System: Dell product: Latitude E6500 serial: 7XFD1J1
          Mobo: Dell model: 0PP476 serial: .7XFD1J1.CN129619122714. Bios: Dell version: A14 date: 07/31/2009
CPU:       Dual core Intel Core2 Duo CPU P8600 (-MCP-) cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx)
          Clock Speeds: 1: 2401.00 MHz 2: 2401.00 MHz
Graphics:  Card: NVIDIA G98M [Quadro NVS 160M]
          X.org: 1.12.4 drivers: nouveau (unloaded: fbdev,vesa) tty size: 137x37 Advanced Data: N/A for root
Audio:     Card: Intel 82801I (ICH9 Family) HD Audio Controller driver: snd_hda_intel
          Sound: Advanced Linux Sound Architecture ver: k3.9-4.towo-siduction-amd64
Network:   Card-1: Broadcom BCM4312 802.11b/g LP-PHY driver: b43-pci-bridge
          IF: wlan0 state: up mac: 00:23:4e:ab:86:7a
          Card-2: Intel 82567LM Gigabit Network Connection driver: e1000e
          IF: eth1 state: down mac: 00:21:70:d4:d3:04
Drives:    HDD Total Size: 120.0GB (44.2% used) 1: id: /dev/sda model: OCZ_VERTEX size: 120.0GB
Partition: ID: / size: 9.8G used: 7.8G (84%) fs: ext4 ID: swap-1 size: 1.61GB used: 0.00GB (0%) fs: swap
RAID:      No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
Sensors:   System Temperatures: cpu: 44.5C mobo: N/A gpu: 42.0
          Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 170 Uptime: 7 min Memory: 884.0/3948.5MB Client: Shell (bash) inxi: 1.9.7

[vilde]

Although I must admit I don't now very much what I'm doing but I belong to those who start and stop my laptop many times a day so I love a fast boot. I just took a chance and installed systemd, and yes it works and yes my laptop goes from grub to log in screen in 6 seconds

This is what I did: Installed systemd, libpam-systemd and systemd-sysv packages, and did put systemd-sysv on hold. Then rebooted.

Maybe or probably I will get into troubles on future d-u:s but that's then...

Edited: Hmm run into problem, the laptop will not shut down when using the menu at xfce, reboot works but not power off. So For now I have to do "poweroff" as root to be able to stop.

My system:

Code Select Expand

Machine:   System: LENOVO product: 6474BB4 version: ThinkPad T400
          Mobo: LENOVO model: 6474BB4 Bios: LENOVO version: 7UET94WW (3.24 ) date: 10/17/2012
CPU:       Dual core Intel Core2 Duo CPU P8600 (-MCP-) cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 9575.98
          Clock Speeds: 1: 800.00 MHz 2: 800.00 MHz
Graphics:  Card: Intel Mobile 4 Series Integrated Graphics Controller bus-ID: 00:02.0
          X.Org: 1.12.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1440x900@60.3hz
          GLX Renderer: Mesa DRI Mobile Intel GM45 Express GLX Version: 2.1 Mesa 8.0.5 Direct Rendering: Yes
Network:   Card-1: Intel Ultimate N WiFi Link 5300 driver: iwlwifi ver: in-tree: bus-ID: 03:00.0
          IF: wlan0 state: up mac: 00:16:ea:e6:27:3a
          Card-2: Intel 82567LM Gigabit Network Connection driver: e1000e ver: 2.2.14-k port: 1840 bus-ID: 00:19.0
          IF: eth0 state: down mac: 00:1c:25:99:37:a2
Drives:    HDD Total Size: 120.0GB (38.3% used) 1: model: KINGSTON_SV300S3
Info:      Processes: 140 Uptime: 8 min Memory: 420.2/3854.4MB Runlevel: 5 Gcc sys: 4.7.3
          Client: Shell (bash 4.2.45) inxi: 1.8.47


[sqlpython]

I have experimented with and am using systemd in Arch/Bridge and Gentoo.
It is forced on you in Arch as is in many Arch spins.
Gentoo my change was by choice just to give it a whirl.
So, I like playing with systemd and the commands but as I use systemd for over a month I began to believe that the boot and process handling was superior to init.d
Simple to add systemd with apt-get and Debian kernels work fine with systemd also.
Of course towo's kernels being specialized may need a tweak or two or three like
CONFIG_DEVTMPFS=y
CONFIG_CGROUPS=y

Then I as in Gentoo I just modified my grub.cfg

Code Select Expand

# $EDITOR /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet init=/lib/systemd/systemd" <--- Change this line

# update-grub
 All seems to work fine but I have no problems with the current init scripting model. Plus, my testing has shown this Distro (Siduction) in particular boots and shuts down as aggressively as my systemd converts.

At the end of the Day for Me, I see no need for systemd. Maybe if it spit fire or something else interesting.
While I am interested to a small Degree my Vote as a user is systemd NO

[devil]

Does anyone have a working journal with systemd? Even though I have libsystemd-journal0 installed, my /var/log is still what it used to be, no /journal.

greetz
devil

[timc]

If I call correctly, there is a simple one-time command to convert to journald logging. It may have been something as simple as creating the directory for it. I am sure there are good instructions on the Arch Wiki.

Tim

[dibl]

Edited: Hmm run into problem, the laptop will not shut down when using the menu at xfce, reboot works but not power off.

I also noticed what looks like a "hang" on restart or power off.  Just wait a minute or two (or three) -- eventually it always completes on my hardware.

@devil I am working on the permanent journal question -- no answer yet.


Edit:  I think I see the problem, down at the bottom of bug 691965.  They could mention that in the wiki ....    

[devil]

Found that by default the journal goes volatile to /run/log. You need to add a line to /etc/systemd/systemd-journald.conf like

Code Select Expand

Storage=persistent to make it go to /var/log/journal. Not very user friendly yet.

greetz
devil

[vilde]

Edited: Hmm run into problem, the laptop will not shut down when using the menu at xfce, reboot works but not power off.

I also noticed what looks like a "hang" on restart or power off.  Just wait a minute or two (or three) -- eventually it always completes on my hardware.

@devil I am working on the permanent journal question -- no answer yet.


Edit:  I think I see the problem, down at the bottom of bug 691965.  They could mention that in the wiki ....    

Looks like it's working to switch of now, yet not failed today and it's fast at switch off also.

[dibl]

Found that by default the journal goes volatile to /run/log. You need to add a line to /etc/systemd/systemd-journald.conf like

Code Select Expand

Storage=persistent to make it go to /var/log/journal.

That works correctly on my desktop system.  On a laptop and a netbook, it does not move the journal -- I still find it at /run/log/journal.  Strange ...