On Thu, 03 Nov 2011 12:41:05 -0400 Michael D. Berger wrote:
> However, in starting a TCP listener socket, from
> "bind(...)" I now get EADDRNOTAVAIL which is
> explained in "man 2 bind", so I am still not
> operational.
Do you use NetworkManager? The network interface may not be up yet when
your s
On Thu, 03.11.11 19:27, Michael D. Berger (m.d.ber...@ieee.org) wrote:
> Which service file? If you mean "myDaemon.service", I don't
> have one; I have "/etc/init.d/myDaemon". Could I put
> options b) or c) in "/etc/init.d/myDaemon"? (I tried it, and
> I didn't start on boot. But maybe my forma
On Thu, 03.11.11 22:11, Michael D. Berger (m.d.ber...@ieee.org) wrote:
> After googing around, here is my first attempt at
> /etc/systemd/system/myDaemon.service:
>
>[Unit]
>Description=myDaemon
>After=syslog.target network.target
>
>[Service]
>ControlGroupAttribute=cpu.rt_ru
I am developing systemd support for ZFS:
https://github.com/zfsonlinux/zfs/pull/435/files
as you can see, I create the units early on bootup using a generator (a
mechanism that is entirely undocumented, tsk).
Then systemd proceeds with normal system startup.
The whole point is to be able to mo
On Fri, Nov 4, 2011 at 13:22, Manuel Amador wrote:
> I am developing systemd support for ZFS:
> as you can see, I create the units early on bootup using a generator (a
> mechanism that is entirely undocumented, tsk).
It isn't documented, because it's use is not encouraged for most use
cases. The
2011/11/4 Manuel Amador :
> I am developing systemd support for ZFS:
>
> https://github.com/zfsonlinux/zfs/pull/435/files
>
> as you can see, I create the units early on bootup using a generator (a
> mechanism that is entirely undocumented, tsk).
>
> Then systemd proceeds with normal system startup
Hi,
here is a new version of the first 3 patches updated as suggested.
The actual /dev/watchdog handling is not part of this series. It needs some
more work to finish.
Regards,
Michael
Michael Olbrich (3):
service: add watchdog timestamp
service: add watchdog restart/reboot timeouts
manage
This patch adds WatchdogTimestamp[Monotonic] to the systemd service
D-Bus API. The timestamp is updated to the current time when the
service calls 'sd_nofity("WATCHDOG=1\n")'.
Using a timestamp instead of an 'alive' flag has two advantages:
1. No timeout is needed to define when a service is no lon
This patch adds the WatchdogRestartSec and WatchdogRebootSec
properties to services. Systemd will restart the service / reboot the
system if the watchdog timeout has not been updated for the configured
amount of time.
This functionality is only enabled if the watchdog timeout is set at
least once.
This patch adds WatchdogRebootTimestamp[Monotonic] to the systemd
manager API. It contains the earliest point in time when systemd might
reboot the system because the timer for WatchdogRebootUSec for a
service expired.
If we assume the system takes Xus to shut down then
WatchdogRebootTimestamp + Xu
> -Original Message-
> From: Lennart Poettering [mailto:lenn...@poettering.net]
> Sent: Friday, November 04, 2011 08:14
> To: Michael D. Berger
> Cc: 'Kay Sievers'; systemd-devel@lists.freedesktop.org
> Subject: Re: [systemd-devel] FW: pthread_create() fails SysV
> in myDaemon on boot
>
On Fri, Nov 04, 2011 at 03:38:40PM +0100, Michael Olbrich wrote:
> This patch adds WatchdogTimestamp[Monotonic] to the systemd service
> D-Bus API. The timestamp is updated to the current time when the
> service calls 'sd_nofity("WATCHDOG=1\n")'.
> Using a timestamp instead of an 'alive' flag has t
On Fri, Nov 04, 2011 at 03:38:41PM +0100, Michael Olbrich wrote:
> This patch adds the WatchdogRestartSec and WatchdogRebootSec
> properties to services. Systemd will restart the service / reboot the
> system if the watchdog timeout has not been updated for the configured
> amount of time.
> This f
On Fri, Nov 04, 2011 at 03:38:42PM +0100, Michael Olbrich wrote:
> This patch adds WatchdogRebootTimestamp[Monotonic] to the systemd
> manager API. It contains the earliest point in time when systemd might
> reboot the system because the timer for WatchdogRebootUSec for a
> service expired.
> If we
> -Original Message-
> From: Michal Schmidt [mailto:mschm...@redhat.com]
> Sent: Friday, November 04, 2011 07:20
> To: Michael D. Berger
> Cc: systemd-devel@lists.freedesktop.org
> Subject: Re: [systemd-devel] FW: pthread_create() fails SysV
> in myDaemon on boot
>
> On Thu, 03 Nov 2011
[...]
Correction! Debug shows the thread is now being created,
so the problem in this thread is solved. Something else
is killing myDaemon in systemd. I'll look further.
Thanks,
Mike.
--
Michael D. Berger
m.d.ber...@ieee.org
http://www.rosemike.net/
_
> -Original Message-
> From: Michael D. Berger [mailto:m.d.ber...@ieee.org]
> Sent: Friday, November 04, 2011 13:12
> To: 'Lennart Poettering'
> Cc: 'Kay Sievers'; 'systemd-devel@lists.freedesktop.org'
> Subject: RE: [systemd-devel] FW: pthread_create() fails SysV
> in myDaemon on boot
>
On 11/04/2011 03:11 AM, Michael D. Berger wrote:
[Service]
ControlGroupAttribute=cpu.rt_runtime_us 50
ExecStart=/usr/sbin/myDaemon --daemon
I'm guessing "--daemon" tells the program to daemonize itself.
In that case you need to add "Type=forking" and "PIDFile=...".
See "man syst
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
"Manuel Amador (Rudd-O)" wrote:
I want systemd to mount file systems in parallel. That is all.
ZFS does not use fstab for the purpose, it has its own zfs mount -a command.
ZFS mount -a will fail when:
/ zfs
/home ext4
> -Original Message-
> From:
> systemd-devel-bounces+m.d.berger=ieee@lists.freedesktop.or
> g
> [mailto:systemd-devel-bounces+m.d.berger=ieee.org@lists.freede
sktop.org] On Behalf Of Michal Schmidt
> Sent: Friday, November 04, 2011 13:36
> To: systemd-devel@lists.freedesktop.org
> Sub
> "Manuel Amador (Rudd-O)" wrote:
>>
>> I want systemd to mount file systems in parallel. That is all.
>>
>> ZFS does not use fstab for the purpose, it has its own zfs mount -a
>> command.
>>
>> ZFS mount -a will fail when:
>>
>> / zfs
>> /home ext4
>> /home/rudd-o zfs
>>
>> As it will attempt to
On Fri, 04 Nov 2011 14:36:05 -0400 Michael D. Berger wrote:
> Your assumption is correct. In the code I have:
> if (argc == 2)
> {
> string arg = argv[1];
> if (arg != "--daemon")
> throw ...
> ::daemon(0,0);
> isDaemon = true;
>
On Thu, 3 Nov 2011 23:07:43 +0100 Lennart Poettering wrote:
> b) Explicitly place your service in the root cgroup of the "cpu"
> controller, by adding "ControlGroup=cpu:/" to the service file.
Michael, have you tried option b) ?
> c) By actually assigning an RT budget to the group, by adding
> "C
> -Original Message-
> From: Michal Schmidt [mailto:mschm...@redhat.com]
> Sent: Friday, November 04, 2011 18:16
> To: Lennart Poettering
> Cc: Michael D. Berger; 'Kay Sievers';
> systemd-devel@lists.freedesktop.org
> Subject: Re: [systemd-devel] FW: pthread_create() fails SysV
> in myDa
> -Original Message-
> From: Michal Schmidt [mailto:mschm...@redhat.com]
> Sent: Friday, November 04, 2011 17:45
> To: Michael D. Berger
> Cc: systemd-devel@lists.freedesktop.org
> Subject: Re: [systemd-devel] FW: pthread_create() fails SysV
> in myDaemon on boot
>
> On Fri, 04 Nov 2011
25 matches
Mail list logo
