Re: [systemd-devel] Zero downtime restart of Web application (Nginx, Puma, JRuby)
On Sat, 18 Jun 2016, at 07:56 PM, Paul Menzel wrote: > Is that possible by just using systemd, or is a load balancer like > HAProxy or a special NGINX configuration and service file templates > needed? I'm looking for answers too and the best switcheroo I've found so far is http://dokku.viewdocs.io/dokku/deployment/zero-downtime-deploys/ which leverages Docker and it's not at all integrated with systemd. Guess a systemd integrated solution would be leveraging machinectl, journalctl and more powerful service control, but I haven't seen an orchestrated deployment like that yet. Maybe CoreOS has something, I am not sure. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Wishlist: HandleLidSwitchDocked ... when powered?
Hi there, I want my T460s machine to suspend on lid close only when it's not charging off mains. I've looked over https://www.freedesktop.org/software/systemd/man/logind.conf.html & https://wiki.archlinux.org/index.php/Power_management and I don't see how this can be achieved. Is it reasonable for me to file a bug on https://github.com/systemd/systemd/ about it? Or am I missing something? Basically I want systemd to consider my laptop being powered by mains as being "docked". I think. Kind regards, ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] UseDNS
I am currently modifying some of the systemd source (specifically the resolved section) and was wondering if you could point me in the right direction. I need access to the UseDNS= setting provided in the .network config files preferably without parsing through them again. Is this data stored anywhere that is available working from the file resolved-resolv-conf.c? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Boot error on PowerPC
Dear systemd developers and maintainers, I incurred in the following error during the boot on a PowerPC based on MPC7410 cpu using systemd v230: systemd[1]: Failed to insert module 'kdbus': Function not implemented random: systemd urandom read with 94 bits of entropy available systemd[1]: Mounting cgroup to /sys/fs/cgroup/devices of type cgroup with options devices. systemd[1]: Mounting cgroup to /sys/fs/cgroup/cpuset of type cgroup with options cpuset. systemd[1]: Mounting cgroup to /sys/fs/cgroup/cpu,cpuacct of type cgroup with options cpu,cpuacct. systemd[1]: Mounting cgroup to /sys/fs/cgroup/debug of type cgroup with options debug. systemd[1]: Mounting cgroup to /sys/fs/cgroup/net_cls of type cgroup with options net_cls. systemd[1]: Mounting cgroup to /sys/fs/cgroup/blkio of type cgroup with options blkio. systemd[1]: Mounting cgroup to /sys/fs/cgroup/memory of type cgroup with options memory. systemd[1]: Mounting cgroup to /sys/fs/cgroup/freezer of type cgroup with options freezer. systemd[1]: systemd 230 running in system mode. (-PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT +GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN) systemd[1]: No virtualization found in DMI systemd[1]: No virtualization found in CPUID systemd[1]: Virtualization XEN not found, /proc/xen/capabilities does not exist systemd[1]: No virtualization found in /proc/device-tree/* systemd[1]: No virtualization found in /proc/cpuinfo. systemd[1]: This platform does not support /proc/sysinfo systemd[1]: Found VM virtualization none systemd[1]: Detected architecture ppc. Welcome to system! systemd[1]: No hostname configured. systemd[1]: Set hostname to . systemd[1]: Initializing machine ID from random generator. systemd[1]: Using cgroup controller name=systemd. File system hierarchy is at /sys/fs/cgroup/systemd. systemd[1]: Installed release agent. systemd[1]: Controller 'cpu' supported: no systemd[1]: Controller 'cpuacct' supported: yes systemd[1]: Controller 'io' supported: yes systemd[1]: Controller 'blkio' supported: yes systemd[1]: Controller 'memory' supported: no systemd[1]: Controller 'devices' supported: yes systemd[1]: Controller 'pids' supported: yes systemd[1]: Set up TFD_TIMER_CANCEL_ON_SET timerfd. systemd[1]: Enabling showing of status. systemd[125]: Spawned /lib/systemd/system-generators/systemd-hibernate-resume-generator as 126. systemd[125]: Spawned /lib/systemd/system-generators/systemd-getty-generator as 127. systemd[125]: Spawned /lib/systemd/system-generators/systemd-gpt-auto-generator as 128. systemd-getty-generator[127]: Automatically adding serial getty for /dev/ttyS0. systemd[125]: Spawned /lib/systemd/system-generators/systemd-debug-generator as 129. systemd[125]: Spawned /lib/systemd/system-generators/systemd-rc-local-generator as 130. systemd[125]: Spawned /lib/systemd/system-generators/systemd-dbus1-generator as 131. random: nonblocking pool is initialized systemd[131]: Failed to execute /lib/systemd/system-generators/systemd-dbus1-generator: Connection reset by peer systemd[125]: /lib/systemd/system-generators/systemd-system-update-generator is empty (a mask). systemd[125]: /lib/systemd/system-generators/systemd-sysv-generator is empty (a mask). systemd[125]: /lib/systemd/system-generators/systemd-fstab-generator is empty (a mask). systemd[125]: /lib/systemd/system-generators/systemd-hibernate-resume-generator succeeded. systemd[130]: Failed to execute /lib/systemd/system-generators/systemd-rc-local-generator: Connection reset by peer systemd[129]: Failed to execute /lib/systemd/system-generators/systemd-debug-generator: Exec format error Core dump to |/bin/false pipe failed systemd[125]: /lib/systemd/system-generators/systemd-dbus1-generator failed with error code 1. systemd[125]: /lib/systemd/system-generators/systemd-gpt-auto-generator failed with error code 127. systemd[125]: /lib/systemd/system-generators/systemd-debug-generator failed with error code 1. systemd[125]: /lib/systemd/system-generators/systemd-rc-local-generator failed with error code 1. systemd[125]: /lib/systemd/system-generators/systemd-getty-generator terminated by signal BUS. systemd[1]: system-generators succeeded. systemd[1]: Failed to stat /etc/systemd/system.control: Input/output error systemd[1]: Failed to stat /etc/systemd/system: Input/output error systemd[1]: Failed to stat /lib/systemd/system: Input/output error systemd[1]: Failed to stat /usr/lib/systemd/system: Input/output error systemd[1]: Looking for unit files in (higher priority first): systemd[1]: /etc/systemd/system.control systemd[1]: /run/systemd/transient systemd[1]: /etc/systemd/system systemd[1]: /run/systemd/system systemd[1]: /lib/systemd/system systemd[1]: /usr/lib/systemd/system systemd[1]: Failed to open directory /etc/systemd/system.control, ignoring: Input/output error systemd[1]: Failed to open directory /etc/systemd/system, ignoring: Input/output error systemd[1]: Failed to open
