On 17/07/14 20:34, Sam Varshavchik wrote:
how systemd chooses, more or less, at random, the order in which to fork
off services it thinks should be started at the same time; in
combination with the time it takes each individual service to start.
That's the hardest thing I find to get my head a
On 17/07/14 20:28, Corinna Vinschen wrote:
boot, it doesn't respond to clients resolution requests until I manually
restart the service after boot. I'll look a bit deeper into that one too and
consider a bug report.
I already reported the bind problem yesterday:
https://bugzilla.redhat.com/sh
On Jul 17 08:34, Sam Varshavchik wrote:
> Despite the outward appearance, systemd is completely ignoring all Before
> and After directives.
No, it's not. You never replied to my mail in the thread you started
a couple of days ago, but before/after do *not* define dependencies.
They define an orde
Ian Chapman writes:
On 17/07/14 18:57, Sam Varshavchik wrote:
Dhcpd on my server has suddenly started taking to start before the IP
address (statically assigned) has been configured on the network
interface and consequently bombs out. The systemd service for dhcpd has
After=network.target
s
On Jul 17 14:28, Corinna Vinschen wrote:
> Hi Ian,
>
> On Jul 17 19:23, Ian Chapman wrote:
> > On 17/07/14 18:45, Corinna Vinschen wrote:
> > >On Jul 17 18:32, Ian Chapman wrote:
> > >>Hi,
> > >>
> > >>Dhcpd on my server has suddenly started taking to start before the IP
> > >>address (statically
Hi Ian,
On Jul 17 19:23, Ian Chapman wrote:
> On 17/07/14 18:45, Corinna Vinschen wrote:
> >On Jul 17 18:32, Ian Chapman wrote:
> >>Hi,
> >>
> >>Dhcpd on my server has suddenly started taking to start before the IP
> >>address (statically assigned) has been configured on the network interface
> >>
On 17/07/14 18:57, Sam Varshavchik wrote:
Dhcpd on my server has suddenly started taking to start before the IP
address (statically assigned) has been configured on the network
interface and consequently bombs out. The systemd service for dhcpd has
After=network.target
should this be network-
On 17/07/14 18:45, Corinna Vinschen wrote:
On Jul 17 18:32, Ian Chapman wrote:
Hi,
Dhcpd on my server has suddenly started taking to start before the IP
address (statically assigned) has been configured on the network interface
and consequently bombs out. The systemd service for dhcpd has
Afte
Ian Chapman writes:
Hi,
Dhcpd on my server has suddenly started taking to start before the IP
address (statically assigned) has been configured on the network interface
and consequently bombs out. The systemd service for dhcpd has
After=network.target
should this be network-online.targe
On Jul 17 18:32, Ian Chapman wrote:
> Hi,
>
> Dhcpd on my server has suddenly started taking to start before the IP
> address (statically assigned) has been configured on the network interface
> and consequently bombs out. The systemd service for dhcpd has
>
> After=network.target
>
>
> should
Hi,
Dhcpd on my server has suddenly started taking to start before the IP
address (statically assigned) has been configured on the network
interface and consequently bombs out. The systemd service for dhcpd has
After=network.target
should this be network-online.target?
--
Ian Chapman.
--
u
11 matches
Mail list logo
