Re: [systemd-devel] systemd-timesync and journalctl questions

2018-09-15 Thread D.S. Ljungmark
On Mon, 10 Sep 2018 at 21:13, Lennart Poettering wrote: > On Fr, 24.08.18 14:52, David Weinehall (david.weineh...@linux.intel.com) > wrote: > > > We're having two time/date related issues/questions: > > > > First of all we'd need some counterpart to ntpdate. > > > > We have a system that lacks

Re: [systemd-devel] Triggering the HW Watchdog

2018-02-27 Thread D.S. Ljungmark
raw...@gmail.com> wrote: > On Tue, Feb 27, 2018 at 6:25 PM, D.S. Ljungmark <ljungm...@modio.se> wrote: >> >> >> >> On 27/02/18 15:21, Lennart Poettering wrote: >> > On Di, 27.02.18 15:12, D.S. Ljungmark (ljungm...@modio.se) wrote: >> > >> >&g

Re: [systemd-devel] Triggering the HW Watchdog

2018-02-27 Thread D.S. Ljungmark
On 27/02/18 15:21, Lennart Poettering wrote: > On Di, 27.02.18 15:12, D.S. Ljungmark (ljungm...@modio.se) wrote: > >>> I figure you can send SIGSTOP to PID 1, no? (there are some signals >>> the kernel blocks for PID 1, but I think SIGSTOP is not among them, >&g

Re: [systemd-devel] Triggering the HW Watchdog

2018-02-27 Thread D.S. Ljungmark
( re-send as I forgot the list ) On 27/02/18 13:20, Lennart Poettering wrote:> On Di, 27.02.18 12:44, D.S. Ljungmark (ljungm...@modio.se) wrote: > >> Hi list! >> >> We're using systemd to control the hardware watchdog, and would want to >> induce fail state to _ve

[systemd-devel] Triggering the HW Watchdog

2018-02-27 Thread D.S. Ljungmark
Hi list! We're using systemd to control the hardware watchdog, and would want to induce fail state to _verify_ that the shutdown/reboot process works as expected. How do we make systemd "fail" to ping the watchdog? How do we control which states ( root fs not available, etc) cause systemd to

Re: [systemd-devel] Illegal CPUID instruction causes systemd core dump

2018-01-05 Thread D.S. Ljungmark
On Fri, Jan 5, 2018 at 6:47 AM, Reindl Harald <h.rei...@thelounge.net> wrote: > > > Am 05.01.2018 um 05:51 schrieb D.S. Ljungmark: >> >> If you want I can bring a small form factor early x86 to Fosdem. >> >> Industrial, rugged little things with x86 ch

Re: [systemd-devel] Illegal CPUID instruction causes systemd core dump

2018-01-04 Thread D.S. Ljungmark
If you want I can bring a small form factor early x86 to Fosdem. Industrial, rugged little things with x86 chipset was rather popular for a while, and you can still order them new. The ones I have aren't i486 but a 586 (cyrix, I think). On Thu, Dec 28, 2017 at 8:26 PM, Reindl Harald

Re: [systemd-devel] "bootctl install" on mdadm raid 1 fails

2017-12-14 Thread D.S. Ljungmark
Right, and _that_ causes a far less interesting output from blkid. /dev/md0: UUID="1492-1FE7" VERSION="FAT32" TYPE="vfat" USAGE="filesystem" On Thu, Dec 14, 2017 at 11:53 AM, Lennart Poettering <lenn...@poettering.net> wrote: > On Do, 14.12.17

Re: [systemd-devel] "bootctl install" on mdadm raid 1 fails

2017-12-14 Thread D.S. Ljungmark
I seem to have the same problem, and here's the output: [root@spring ~]# blkid -p /dev/sda1 /dev/sda1: UUID="01c0c70f-9204-8e4e-f2a7-aa8ec14c4a41" UUID_SUB="2a820238-597c-bfd4-aa2e-19425f7e8fa4" LABEL="spring.skuggor.se:0" VERSION="1.0" TYPE="linux_raid_member" USAGE="raid"

Re: [systemd-devel] Scheduling unit at reboot.target and shutdown.target

2017-10-27 Thread D.S. Ljungmark
On 27/10/17 12:25, Lennart Poettering wrote: > On Fr, 27.10.17 11:43, D.S. Ljungmark (spi...@aanstoot.se) wrote: > >> So, I've got a piece of hardware I want to do a final handover to just >> around reboot.target / shutdown.target >> >> This will then cause the ent

[systemd-devel] Scheduling unit at reboot.target and shutdown.target

2017-10-27 Thread D.S. Ljungmark
So, I've got a piece of hardware I want to do a final handover to just around reboot.target / shutdown.target This will then cause the entire CPU and hardware allocated to it to actually drop power (and schedule re-power), so I don't want to do this earlier. Is it simply to do: [Unit]

Re: [systemd-devel] systemd should not depend on CONFIG_CRYPTO_USER_API_HASH

2017-03-20 Thread D.S. Ljungmark
I find your argument to be strange. "The kernel has this functionality, please do not use it and rather reimplement it in every piece of userspace that ever needs it, because that's supposed to be more secure." I simply don't buy your argument here. //D.S. On Mon, Mar 20, 2017 at 8:22 AM, Eric

Re: [systemd-devel] [networkd] Mixing DHCP & static IPs on 1 interface

2017-02-22 Thread D.S. Ljungmark
On 22/02/17 15:57, Reindl Harald wrote: > > please keep repsonses on the list > > Am 22.02.2017 um 15:42 schrieb Ian Pilcher: >> On 02/21/2017 08:28 PM, Reindl Harald wrote: >>> since this should be all on the LAN side something is *very* unusual on >>> your setup - the firewall i setup at

Re: [systemd-devel] systemd-journald error

2016-11-30 Thread D.S. Ljungmark
On 25/11/16 22:47, Joel wrote: > Lennart - > > > Thank you for the reply. > > > It's not clear whether you are instructing me to do something > (restart journald or rebuild initrd) or asking a question. If your distribution builds in the config file into the initrd, it's not enough to

Re: [systemd-devel] Munge start Error

2016-11-17 Thread D.S. Ljungmark
On 17/11/16 13:11, JEYARAJ wrote: > Hi All, > > Dear Sir, > I ,am installing job scheduling system for a single machine.munge also > installed latest version. > I start with Munge service .Error is showing; > > Again I used the command: > > Systemctl status munge.service > > Error is came.

[systemd-devel] Multiple starts of a service, what am I doing wrong?

2015-09-24 Thread D.S. Ljungmark
I've got the following unit: [Unit] Description=Random Submitter Wants=network-online.target After=network-online.target other.service RequiresMountsFor=/data [Service] Type=simple Environment=PYTHONPATH=/data PrivateTmp=false # Launches client config and others if needed

Re: [systemd-devel] Multiple starts of a service, what am I doing wrong?

2015-09-24 Thread D.S. Ljungmark
(re-send due to wrong email address) On 24/09/15 14:38, Daniel Mack wrote: > On 09/24/2015 01:17 PM, D.S. Ljungmark wrote: >> I've got the following unit: >> >> [Unit] >> Description=Random Submitter >> Wants=network-online.target >> After=network-online.ta

[systemd-devel] Unit files on another partition

2014-12-12 Thread D.S. Ljungmark
hi, Our / partitions are on a squashfs media, which means that unit files are read-only. There is a partition for read-write content (Scratchable), and I'm wondering if it would be possible to add unit-files there and have the boot order cope with this correctly? How should this be set up

Re: [systemd-devel] Journal, rotation and loglevels

2014-12-02 Thread D.S. Ljungmark
On 24/10/14 00:47, Lennart Poettering wrote: On Thu, 23.10.14 17:19, D.S. Ljungmark (spi...@aanstoot.se) wrote: On 23/10/14 16:50, Lennart Poettering wrote: On Thu, 23.10.14 15:27, D.S. Ljungmark (spi...@aanstoot.se) wrote: Hi, we have a few services that are spamming a fair bit

Re: [systemd-devel] Service not restarting after Condition failed

2014-11-25 Thread D.S. Ljungmark
On 24/11/14 20:30, Umut Tezduyar Lindskog wrote: Hi On Monday, November 24, 2014, D.S. Ljungmark spi...@aanstoot.se mailto:spi...@aanstoot.se wrote: On 10/11/14 23:09, Lennart Poettering wrote: On Thu, 30.10.14 18:47, D.S. Ljungmark (spi...@aanstoot.se javascript:;) wrote

[systemd-devel] Watchdog timeout signals

2014-11-24 Thread D.S. Ljungmark
Hi, We're pondering to use the WatchdogSec=.. function, but wanted to know what signal (if any) are sent to the application before termination. Main reason is that we want to get a proper stacktrace of the daemon if it is killed for some reason. //D.S. -- 8362 CB14 98AD 11EF CEB6 FA81 FCC3

Re: [systemd-devel] Watchdog timeout signals

2014-11-24 Thread D.S. Ljungmark
On 24/11/14 17:58, Peter Sztanojev wrote: On Mon, Nov 24, 2014 at 5:39 PM, D.S. Ljungmark spi...@aanstoot.se wrote: Hi, We're pondering to use the WatchdogSec=.. function, but wanted to know what signal (if any) are sent to the application before termination. Main reason is that we want

Re: [systemd-devel] Service not restarting after Condition failed

2014-11-24 Thread D.S. Ljungmark
On 10/11/14 23:09, Lennart Poettering wrote: On Thu, 30.10.14 18:47, D.S. Ljungmark (spi...@aanstoot.se) wrote: Hi we have a service set to: ConditionFileNotEmpty= and Restart=Always This combination would (in my feebled mind) cause the service to restart once the Condition

[systemd-devel] Service not restarting after Condition failed

2014-10-30 Thread D.S. Ljungmark
Hi we have a service set to: ConditionFileNotEmpty= and Restart=Always This combination would (in my feebled mind) cause the service to restart once the Condition was fulfilled, but that doesn't seem to be the case. Is there a way I can get a service to restart even after it has been set as

[systemd-devel] Journal, rotation and loglevels

2014-10-23 Thread D.S. Ljungmark
Hi, we have a few services that are spamming a fair bit on DEBUG level of log output. In syslog, we'd separate the DEBUG logs from the main log, and set the rotation of DEBUG+ to be ~24 hours, while keeping INFO and above for ~4 weeks. How can we do something similar with Journald? Keeping all

Re: [systemd-devel] Journal, rotation and loglevels

2014-10-23 Thread D.S. Ljungmark
On 23/10/14 16:50, Lennart Poettering wrote: On Thu, 23.10.14 15:27, D.S. Ljungmark (spi...@aanstoot.se) wrote: Hi, we have a few services that are spamming a fair bit on DEBUG level of log output. In syslog, we'd separate the DEBUG logs from the main log, and set the rotation of DEBUG