Hi,
I have the following setup:
* home made router that I configured all on my own including
compilation, running dnsmasq to provide everything from dhcp to slaac
and dns.
* said dnsmasq has no dnssec support. It is neither compiled in the
binary nor set up in the dnsmasq.conf file.
* systemd-
look, but I didn't find anything suspicious in journalctl or
dmesg.
Thanks
Lennart Poettering a écrit :
On Mo, 29.04.19 11:06, Ellis ([email protected]) wrote:
Hi,
after some manual testing on my end, I can confirm two things:
1. systemd really takes care of /run as it should
and 2. I
x27;m even more confused.
Thanks for the help, really appreciate it
Lennart Poettering a écrit :
On Mo, 29.04.19 07:12, Ellis ([email protected]) wrote:
Hi,
thank you once again. I guess I will have to find how to keep this directory
as a whole as you said. Maybe I expected systemd to realize
Hi,
subject pretty much says it all. I am currently working on an embeded
system and wish to use systemd in both the rootfs and the initramfs.
These are both built via buildroot, making a full rootfs for one and a
minimal rootfs for the other. However the documentation on how to make a
proper
On 04/02/12 10:04, Warpme wrote:
On 2/1/12 8:37 PM, Chris Paulson-Ellis wrote:
On 01/02/12 19:07, Lennart Poettering wrote:
On Wed, 01.02.12 18:54, Chris Paulson-Ellis ([email protected]) wrote:
Is there some way to get the client to always restart when server
restarts, for whatever reason
The reaping of generator processes run as part of a daemon-reload should not
call waitid(PID_ALL). The waitid() call in execute_directory() is intended only
to reap the executed processes, but if a service process exits at about the
same time as a daemon-reload, then that service process is reaped
On 01/02/12 19:26, Lennart Poettering wrote:
On Wed, 01.02.12 19:13, Chris Paulson-Ellis ([email protected]) wrote:
On 01/02/12 19:07, Lennart Poettering wrote:
On Wed, 01.02.12 18:54, Chris Paulson-Ellis ([email protected]) wrote:
Is there some way to get the client to always restart when
On 01/02/12 19:05, Lennart Poettering wrote:
(As I figured out newer Intel chipsets all have watchdogs now, so I am
actually quite keen to see this implemented in systemd now, since I can
actually test it.)
Just a warning to anyone who's thinking of depending on the chipset
watchdog... In my e
On 01/02/12 19:07, Lennart Poettering wrote:
On Wed, 01.02.12 18:54, Chris Paulson-Ellis ([email protected]) wrote:
Is there some way to get the client to always restart when server
restarts, for whatever reason?
No, there isn't. But what you describe is something I consider a bug,
and t
I've got a client service (client.service) that requires a server
service (server.service). They are weakly coupled by a polling http
protocol, but the client needs to restart when server does or it can get
into trouble in it's state machine (and can't easily be re-coded to cope).
If I use Req
I'm having trouble getting my head round how hotplugged device
activation should work with systemctl enable/disable.
I have a udev rule that uses ENV{SYSTEMD_WANTS}="foo@%k.service" to hook
device hotplug to systemd and a template unit file for [email protected] that
uses BindTo=dev-%i.device to en
Hi,
I'm running a Java JVM service using:
ExecStart=/usr/bin/java -jar foo.jar
When I stop the service with systemctl, it goes into the failed state
because the JVM exits with status 143 instead of 0.
There doesn't seem to be any way to get a JVM to exit(0) on SIGTERM. You
can run code on t
12 matches
Mail list logo
