On 07/06/2014 03:17 AM, Sam Varshavchik wrote:
Ed Greshko writes:
Hilarity ensues.
Any plans to bugzilla your issue? It should be fun to follow.
Well, I thought about this. For about 30 seconds.
I'm going to say something controversial now. It'll likely send some flames
my way; and my et
On 07/05/2014 02:58 PM, Sam Varshavchik wrote:
...
Actually, I think we do have a sliver of hope, now that systemd has infested
RHEL. As RHEL 7 rolls out, complete with the systemd clusterfrak, it's now
going to get some exposure to Red Hat's paying customers. Expect some noise
to slowly increase
Ed Greshko writes:
Did you just fix your problem or did you also bugzilla it?
I was having trouble getting into bugzilla and set it aside. But I've
revisited this: https://bugzilla.redhat.com/show_bug.cgi?id=1116539
--
David Benfell
See https://parts-unknown.org/node/2 if you do not unde
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/06/14 09:17, Sam Varshavchik wrote:
> Ed Greshko writes:
>
>> >
>> > Hilarity ensues.
>>
>> Any plans to bugzilla your issue? It should be fun to follow.
>
> Well, I thought about this. For about 30 seconds.
>
> I'm going to say something contr
Ed Greshko writes:
>
> Hilarity ensues.
Any plans to bugzilla your issue? It should be fun to follow.
Well, I thought about this. For about 30 seconds.
I'm going to say something controversial now. It'll likely send some flames
my way; and my ethics will get questioned. Maybe, I suppose,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/06/14 08:32, Sam Varshavchik wrote:
> Ed Greshko writes:
>
>> On 07/06/14 07:28, Sam Varshavchik wrote:
>> > Ed Greshko writes:
>> >
>> >> > The server with dhcp, httpd, named, and privoxy does not have
>> >> > NetworkManager installed. Both th
Ed Greshko writes:
On 07/06/14 07:28, Sam Varshavchik wrote:
> Ed Greshko writes:
>
>> > The server with dhcp, httpd, named, and privoxy does not have
NetworkManager installed. Both the WAN and the LAN ports are configured as
static IPs.
>>
>> You may want to try NetworkManager and wait-onl
On Sat, 05 Jul 2014 20:17:53 -0400
Sam Varshavchik wrote:
> Kevin Fenzi writes:
>
> > On Sat, 05 Jul 2014 19:30:06 -0400
> > Sam Varshavchik wrote:
> >
> > > R. G. Newbury writes:
> > >
> > > >>
> > > >> That at least works up to the day systemd decides
> > > >> no one needs rc.local and they d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/06/14 08:22, David Benfell wrote:
> Ed Greshko writes:
>>
>> I suppose the bottom line is I can't confirm your issue. I've not made any
>> changes to the default systemd config or service files.
>
> I guess I get to call dibs here. This issue
Ed Greshko writes:
I suppose the bottom line is I can't confirm your issue. I've not made
any changes to the default systemd config or service files.
I guess I get to call dibs here. This issue is the one that bedeviled me
with postfix (and nsd and ejabberd), and the solution, using netwo
Kevin Fenzi writes:
On Sat, 05 Jul 2014 19:30:06 -0400
Sam Varshavchik wrote:
> R. G. Newbury writes:
>
> >>
> >> That at least works up to the day systemd decides
> >> no one needs rc.local and they drop support for
> >> it (a day that is sure to come :-).
> >
> > Direct support for rc.local
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/06/14 07:32, Kevin Fenzi wrote:
> On Sat, 05 Jul 2014 19:30:06 -0400
> Sam Varshavchik wrote:
>
>> R. G. Newbury writes:
>>
That at least works up to the day systemd decides
no one needs rc.local and they drop support for
it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/06/14 07:28, Sam Varshavchik wrote:
> Ed Greshko writes:
>
>> > The server with dhcp, httpd, named, and privoxy does not have
>> > NetworkManager installed. Both the WAN and the LAN ports are configured as
>> > static IPs.
>>
>> You may want t
On Sat, 05 Jul 2014 19:30:06 -0400
Sam Varshavchik wrote:
> R. G. Newbury writes:
>
> >>
> >> That at least works up to the day systemd decides
> >> no one needs rc.local and they drop support for
> >> it (a day that is sure to come :-).
> >
> > Direct support for rc.local has already been "depr
R. G. Newbury writes:
That at least works up to the day systemd decides
no one needs rc.local and they drop support for
it (a day that is sure to come :-).
Direct support for rc.local has already been "deprecated". Somewhere I read
something from Lennart and it was clear that he has an almo
Ed Greshko writes:
> The server with dhcp, httpd, named, and privoxy does not have
NetworkManager installed. Both the WAN and the LAN ports are configured as
static IPs.
You may want to try NetworkManager and wait-online. WAN links can take time
to become active.
NetworkManager does no
On Sat, 05 Jul 2014 08:13:45 -0400
Sam Varshavchik wrote:
Everything was always broken
I'm pretty sure everything was always broken.
I never had the combination of postfix, dovecot,
and stunnel operational more than about 10% of
the time with pure systemd.
I just took a more practical approac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/06/14 01:00, Sam Varshavchik wrote:
> Ed Greshko writes:
>
>> On 07/05/14 20:13, Sam Varshavchik wrote:
>> > So, how should this mess get fixed? Start filing bugs against all these
>> > packages, requesting a change to their systemd service fil
Ed Greshko writes:
On 07/05/14 20:13, Sam Varshavchik wrote:
> So, how should this mess get fixed? Start filing bugs against all these
packages, requesting a change to their systemd service file, to state a
dependency on network-online.target?
FWIW, I'm running a fully updated F20 system a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/05/14 20:13, Sam Varshavchik wrote:
> So, how should this mess get fixed? Start filing bugs against all these
> packages, requesting a change to their systemd service file, to state a
> dependency on network-online.target?
FWIW, I'm running a
On Sat, 05 Jul 2014 08:58:23 -0400
Sam Varshavchik wrote:
> it's now
> going to get some exposure to Red Hat's paying customers
And since the 'E' in RHEL is "Enterprise", I suspect
many of those customers are going to wonder why
systemd needs to hang around and consume vast amounts
of resources
Tom Horsley writes:
On Sat, 05 Jul 2014 08:13:45 -0400
Sam Varshavchik wrote:
> Everything was always broken
I'm pretty sure everything was always broken.
I never had the combination of postfix, dovecot,
and stunnel operational more than about 10% of
the time with pure systemd.
For me, every
On Sat, 05 Jul 2014 08:13:45 -0400
Sam Varshavchik wrote:
> Everything was always broken
I'm pretty sure everything was always broken.
I never had the combination of postfix, dovecot,
and stunnel operational more than about 10% of
the time with pure systemd.
I just took a more practical approach
It looks like after the last systemd update, systemd appears to start jobs
that have a dependency on network availability before the network is
actually up.
After booting, a crapload of services reliably fail to start: httpd, dhcpd,
named, and others. All of them come up fine if I manually
24 matches
Mail list logo
