[systemd-devel] Seeing kernel timestamps in journal
My kernel dmesg log looks like: [133940.153317] connect failed event=0 e->status 1 e->reason 0 [133940.154245] CFG80211-ERROR) wl_bss_connect_done : Report connect result - connection failed [133944.489326] CFG80211-ERROR) wl_cfg80211_connect : Connectting with00:14:d1:61:da:57 channel (6) ssid "teforia-mfg1", len (12) [133944.489326] [133944.574628] wl_bss_connect_done succeeded with 00:14:d1:61:da:57 [133944.650060] wl_bss_connect_done succeeded with 00:14:d1:61:da:57 The equivalent from journalctl -k is: Nov 13 15:02:08 teforia-fzeda511d00nya501 kernel: connect failed event=0 e->status 1 e->reason 0 Nov 13 15:02:08 teforia-fzeda511d00nya501 kernel: CFG80211-ERROR) wl_bss_connect_done : Report connect result - connection failed Nov 13 15:02:12 teforia-fzeda511d00nya501 kernel: CFG80211-ERROR) wl_cfg80211_connect : Connectting with00:14:d1:61:da:57 channel (6) ssid "teforia-mfg1", len (12) Nov 13 15:02:12 teforia-fzeda511d00nya501 kernel: wl_bss_connect_done succeeded with 00:14:d1:61:da:57 Nov 13 15:02:12 teforia-fzeda511d00nya501 kernel: wl_bss_connect_done succeeded with 00:14:d1:61:da:57 How do I get the kernel timestamps to come out of journalctl? I'm running journalctl on intel edison: systemd 213 -PAM -AUDIT -SELINUX +IMA +SYSVINIT -LIBCRYPTSETUP -GCRYPT +ACL +XZ -SECCOMP -APPARMOR marty ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Disabling Predictable Network Interface Names by masking 80-net-setup-link.rules
Hi, On the Predictable Network Interface Names wiki page [1], one of the option for disabling predictable network interface names is to mask the 80-net-setup-link.rules udev rule. This has a side effect of somewhat breaking systemd-network: net_setup_link builtin is not run and the ID_NET_DRIVER udev property is not set on the interface. Consequently, the .network files that match against a driver (such as /usr/lib/systemd/network/80-container-ve.network) don't pick up the interface. I encountered that issue when trying to use --network-veth with systemd-nspawn on the Fedora cloud image (where 80-net-setup-link.rules is masked). In this case, network is not available in the container and it can be tricky to understand why. So I would suggest to update that wiki page. Here's an alternative for udev: cat /usr/lib/udev/rules.d/80-net-setup-link.rules | grep -v NAME= > /etc/udev/rules.d/80-net-setup-link.rules Sylvain [1] http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Disabling Predictable Network Interface Names by masking 80-net-setup-link.rules
14.11.2016 00:51, Sylvain Pasche пишет: > Hi, > > On the Predictable Network Interface Names wiki page [1], one of the option > for disabling predictable network interface names is to mask the > 80-net-setup-link.rules udev rule. > > This has a side effect of somewhat breaking systemd-network: net_setup_link > builtin is not run and the ID_NET_DRIVER udev property is not set on the > interface. > Consequently, the .network files that match against a driver (such as > /usr/lib/systemd/network/80-container-ve.network) don't pick up the interface. > > I encountered that issue when trying to use --network-veth with > systemd-nspawn on the Fedora cloud image (where 80-net-setup-link.rules is > masked). In this case, network is not available in the container and it can > be tricky to understand why. > > So I would suggest to update that wiki page. Here's an alternative for udev: > cat /usr/lib/udev/rules.d/80-net-setup-link.rules | grep -v NAME= > > /etc/udev/rules.d/80-net-setup-link.rules yuck. Does net.ifnames=0 not work for you? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
