On Sat, Nov 4, 2017 at 6:57 AM, Sam Varshavchik wrote:
> privoxy.service most certainly has:
>
> Wants=network-online.target
> After=network-online.target
...
> However, privoxy just failed to start for me, after a reboot.
I was curious about this, so I went back to the beginning. I take
back w
Allegedly, on or about 7 November 2017, Sam Varshavchik sent:
> You are proposing to modify each upstream package to inject custom
> code that will wait for all IP addresses to be configured, before
> proceeding?
>
> And you think this is easier, and more maintanable, then simply
> fixing the brok
Tim writes:
Allegedly, on or about 5 November 2017, Sam Varshavchik sent:
> Now, as I see it, this boils down to a one word, simple question:
>
> Why?
>
> Do we really expect that one should actually do that?
>
> Using privoxy as an illustrative example: is it really so
> unreasonable to expect
Allegedly, on or about 5 November 2017, Sam Varshavchik sent:
> Now, as I see it, this boils down to a one word, simple question:
>
> Why?
>
> Do we really expect that one should actually do that?
>
> Using privoxy as an illustrative example: is it really so
> unreasonable to expect that install
Tom H writes:
On Sun, Nov 5, 2017 at 8:10 PM, Sam Varshavchik
wrote:
> Gordon Messmer writes:
>> On 11/05/2017 05:36 AM, Sam Varshavchik wrote:
>>> Unfortunately, with systemd, nobody really knows how it works,
>>> apparently.
>>
>> There do appear to be a few people here who don't understa
On Sun, Nov 5, 2017 at 8:10 PM, Sam Varshavchik wrote:
> Gordon Messmer writes:
>> On 11/05/2017 05:36 AM, Sam Varshavchik wrote:
>>> Unfortunately, with systemd, nobody really knows how it works,
>>> apparently.
>>
>> There do appear to be a few people here who don't understand how it works,
>>
On Sun, 05 Nov 2017 19:54:11 -0500 Sam Varshavchik wrote:
> I have a better idea. How about "network-wait-online.service, or whatever
> it's called, and whatever other services that need to be enabled, are
> enabled by default".
> If a service, like privoxy, requires all interfaces to be up,
>
> Unfortunately, with systemd, nobody really knows how it works, apparently.
>>
>
>
> There do appear to be a few people here who don't understand how it works,
> but that's hardly systemd's fault. This specific subject is documented
> thoroughly:
>
> https://www.freedesktop.org/wiki/Software/sy
Gordon Messmer writes:
On 11/05/2017 05:36 AM, Sam Varshavchik wrote:
Unfortunately, with systemd, nobody really knows how it works, apparently.
There do appear to be a few people here who don't understand how it works,
but that's hardly systemd's fault. This specific subject is documente
Tom Horsley writes:
On Sun, 5 Nov 2017 14:19:47 -0800
Mike Wright wrote:
> I like that. Maybe something like a "systemd-networkd-wait-online.d
> directory that contains files named for the interfaces that have to be
> up and IP'd.
Then you find everything stops working when you get another
ke
On Sun, 5 Nov 2017 14:19:47 -0800
Mike Wright wrote:
> I like that. Maybe something like a "systemd-networkd-wait-online.d
> directory that contains files named for the interfaces that have to be
> up and IP'd.
Then you find everything stops working when you get another
kernel update that brea
On 11/05/2017 01:59 PM, Tom H wrote:
On Sun, Nov 5, 2017 at 3:02 PM, wrote:
On Sun, 05 Nov 2017 14:33:42 -0500 Tom H wrote:
On Sun, Nov 5, 2017 at 12:41 PM, wrote:
On Sun, 05 Nov 2017 12:24:15 -0500 Tom H wrote:
In the networkd case, you can specify an interface
Right but that is probabl
On 11/05/2017 06:18 AM, Tom Horsley wrote:
Because systemd is brought to you by the same people that
brought you NetworkManager
Yes, if you define "the same people" as "Red Hat." But in that case, a
great deal of the GNU/Linux stack, including gcc, glibc, and Linux (the
kernel) are brought
On 11/05/2017 05:36 AM, Sam Varshavchik wrote:
Unfortunately, with systemd, nobody really knows how it works, apparently.
There do appear to be a few people here who don't understand how it
works, but that's hardly systemd's fault. This specific subject is
documented thoroughly:
https://w
On Sun, Nov 5, 2017 at 3:02 PM, wrote:
> On Sun, 05 Nov 2017 14:33:42 -0500 Tom H wrote:
>> On Sun, Nov 5, 2017 at 12:41 PM, wrote:
>>> On Sun, 05 Nov 2017 12:24:15 -0500 Tom H wrote:
In the networkd case, you can specify an interface
>>>
>>> Right but that is probably useless since:
>>
On Sun, 05 Nov 2017 14:33:42 -0500 Tom H wrote:
> On Sun, Nov 5, 2017 at 12:41 PM, wrote:
>> On Sun, 05 Nov 2017 12:24:15 -0500 Tom H wrote:
>>> In the networkd case, you can specify an interface
>> Right but that is probably useless since:
>> systemd-networkd-wait-online is a one-shot system
On Sun, Nov 5, 2017 at 12:41 PM, wrote:
> On Sun, 05 Nov 2017 12:24:15 -0500 Tom H wrote:
>>
>> In the networkd case, you can specify an interface
>
> Right but that is probably useless since:
>
> systemd-networkd-wait-online is a one-shot system service that waits
> for the network to be configur
On Sun, 05 Nov 2017 12:24:15 -0500 Tom H wrote:
> On Sun, Nov 5, 2017 at 11:22 AM, Justin Moore
> wrote:
>> The challenge here is that systemd considers "the network" to be up if
>> *any* networking devices are up.
Probably only in the NetworkManager case:
When run, nm-online waits until Ne
On Sun, Nov 5, 2017 at 11:22 AM, Justin Moore wrote:
>
> The challenge here is that systemd considers "the network" to be up if
> *any* networking devices are up. I ran into this on my MythTV setup,
> where once the InfiniTV capture card was up (which uses a virtual
> network interface), systemd w
The challenge here is that systemd considers "the network" to be up if
*any* networking devices are up. I ran into this on my MythTV setup, where
once the InfiniTV capture card was up (which uses a virtual network
interface), systemd would give the green light for every other service to
start up. O
On Sun, Nov 5, 2017 at 8:52 AM, Sam Varshavchik wrote:
> Tom H writes:
>> On Sun, Nov 5, 2017 at 12:48 AM, Sam Varshavchik
>> wrote:
>>>
>>> If the packaging guidelines are for a package dependency on
>>> network-online.target, and especially if NetworkManager is installed
>>> by default – as it
On Sun, Nov 5, 2017 at 8:36 AM, Sam Varshavchik wrote:
> Samuel Sieb writes:
>>
>> What would that even mean? That service has no meaning by itself. Of
>> course, NetworkManager will start the network interfaces even without it.
>> The whole purpose of that service is to delay any other services t
Hi.
On Sun, 05 Nov 2017 08:52:33 -0500 Sam Varshavchik wrote:
> Why is it so difficult to make sure that a service gets started after all IP
> addresses are set up by the system, for services that have this requirement?
Using a dependency (Wants and After) to network-online.target is the
prop
Tom Horsley writes:
On Sun, 05 Nov 2017 08:52:33 -0500
Sam Varshavchik wrote:
> Why is it so difficult to make sure that a service gets started after all
IP
> addresses are set up by the system, for services that have this
requirement?
Because systemd is brought to you by the same people
On Sun, 05 Nov 2017 08:52:33 -0500
Sam Varshavchik wrote:
> Why is it so difficult to make sure that a service gets started after all IP
> addresses are set up by the system, for services that have this requirement?
Because systemd is brought to you by the same people that
brought you NetworkMa
Tom H writes:
On Sun, Nov 5, 2017 at 12:48 AM, Sam Varshavchik
wrote:
> If the packaging guidelines are for a package dependency on
> network-online.target, and especially if NetworkManager is installed
> by default – as it is, then it seems wrong not to have this enabled by
> default.
Would
Samuel Sieb writes:
What would that even mean? That service has no meaning by itself. Of
course, NetworkManager will start the network interfaces even without it.
The whole purpose of that service is to delay any other services that
require the network to be started before running.
See
On Sun, Nov 5, 2017 at 12:48 AM, Sam Varshavchik wrote:
> Tom H writes:
>
>>> 192.168.0.1 is a static IP address. DHCP is not in the picture here. I
>>> created bug 1509544 for this, but I am not holding any illusions, here.
>>
>> Is "NetworkManager-wait-online.service" or
>> "systemd-networkd-wai
On 11/04/2017 09:48 PM, Sam Varshavchik wrote:
Looks like systemd-networkd-wait-online.service is disabled by default
in Fedora.
Given that there are packages that require all IP addresses to be
configured, and thus declare a dependency on network-online.target, it
does not seem logical for N
Tom H writes:
> 192.168.0.1 is a static IP address. DHCP is not in the picture here. I
> created bug 1509544 for this, but I am not holding any illusions, here.
Is "NetworkManager-wait-online.service" or
"systemd-networkd-wait-online.service" enabled?
If you're using "/etc/rc.d/init.d/network"
On Sat, Nov 4, 2017 at 11:14 AM, Greg Woods wrote:
> On Sat, Nov 4, 2017 at 9:51 AM, Tom Horsley wrote:
>>
>> Systemd has no idea what "up" means for networking
>
> More accurately, the network-online.target doesn't mean what a reasonable
> person would think it means. It actually means that the
On Sat, Nov 4, 2017 at 9:57 AM, Sam Varshavchik wrote:
>
> privoxy.service most certainly has:
>
> Wants=network-online.target
> After=network-online.target
>
> I'm staring at this service file, right now.
>
> I have privoxy binding to an internal IP address, of course:
>
> listen-address 192.168
On Sat, Nov 4, 2017 at 9:51 AM, Tom Horsley wrote:
>
>
> Systemd has no idea what "up" means for networking
>
More accurately, the network-online.target doesn't mean what a reasonable
person would think it means. It actually means that the base network
drivers have been loaded, not that all the
On Sat, 04 Nov 2017 09:57:11 -0400
Sam Varshavchik wrote:
> Would anyone care to guess what the problem is
Systemd has no idea what "up" means for networking.
I have to start every service that needs the network
to be up from rc.local with a time delay.
___
privoxy.service most certainly has:
Wants=network-online.target
After=network-online.target
I'm staring at this service file, right now.
I have privoxy binding to an internal IP address, of course:
listen-address 192.168.0.1:8000
However, privoxy just failed to start for me, after a reboot.
35 matches
Mail list logo
