Mailing List Archive

Strange output when restarting network. Long term issue.
Howdy,

It has been doing this for as long as I can recall.  I'm pretty sure it
did this on my old system before this one as well.  This is what it does. 

root@fireball / # /etc/init.d/net.eth1 restart
 * Caching service dependencies
...                                                                                                                                          
[ ok ]
 * Unmounting network filesystems
...                                                                                                                                        
[ ok ]
 * Bringing down interface eth1
 *   Stopping dhcpcd on eth1 ...
sending signal TERM to pid 2852
waiting for pid 2852 to
exit                                                                                                                                                 
[ ok ]
 * Bringing up interface eth1
 *   dhcp ...
 *     Running dhcpcd ...
DUID 00:99:00:01:1d:ab:d4:a4:00:01:35:80:cd:35
eth1: IAID 35:80:cd:35
eth1: adding address fe80::9dbe:4ab5:f194:3602
eth1: soliciting an IPv6 router
eth1: rebinding lease of 192.168.0.100
eth1: probing address 192.168.0.100/24
eth1: leased 192.168.0.100 for 7200 seconds
eth1: adding route to 192.168.0.0/24
eth1: adding default route via 192.168.0.1
forked to background, child pid
16225                                                                                                                                        
[ ok ]
 *     received address
192.168.0.100/24                                                                                                                                     
[ ok ]
root@fireball / #  * Mounting network filesystems
...                                                                                                                        
[ ok ]

root@fireball / #

See how it receives the address from the router and then gives a prompt
again, then it mounts network file systems where I should type in a
command but that isn't me..  To get a prompt again, I have to hit the
return key.  Why does it give me a prompt when it isn't done yet? 
Shouldn't it finish completely before returning to a prompt?  This is in
a Konsole, within KDE.  That said, I'm pretty sure it does this on a
console, ctrl alt F*, screen as well. 

While this doesn't break anything, it is sort of annoying.  Maybe I have
a setting wrong somewhere?  Maybe there is a bad default setting?  Maybe
it does this for all of us?

Just curious what it up with this. 

Dale

:-)  :-) 
Re: Strange output when restarting network. Long term issue. [ In reply to ]
On Wed, Jul 22, 2020 at 09:13:22PM -0500, Dale wrote:
> See how it receives the address from the router and then gives a prompt
> again, then it mounts network file systems where I should type in a
> command but that isn't me..? To get a prompt again, I have to hit the
> return key.? Why does it give me a prompt when it isn't done yet??
> Shouldn't it finish completely before returning to a prompt?? This is in
> a Konsole, within KDE.? That said, I'm pretty sure it does this on a
> console, ctrl alt F*, screen as well.?

I can confirm I get this also, using st (suckless/simple terminal). I have a VPN
script in my net.eno1 script, so the output might differ slightly from yours,
although the strange behaviour seems the same.

[super] root@ad-gentoo-main / # etc/init.d/net.eno1 restart
* Stopping openvpn ... [ ok ]
* Unmounting network filesystems ... [ ok ]
* Bringing down interface eno1
* Stopping dhcpcd on eno1 ...
sending signal TERM to pid 13839
waiting for pid 13839 to exit [ ok ]
* Bringing up interface eno1
* dhcp ...
* Running dhcpcd ...
DUID 00:04:aa:aa:aa:aa:aa:aa:aa:aa:aa:aa:d8:cb:8a:c6:64:cd
eno1: IAID 8a:c6:64:cd
eno1: adding address fe80::fd5:dd1a:7c1c:f59c
eno1: rebinding lease of 192.168.0.3
eno1: carrier lost
eno1: deleting address fe80::fd5:dd1a:7c1c:f59c
eno1: carrier acquired
eno1: IAID 8a:c6:64:cd
eno1: adding address fe80::fd5:dd1a:7c1c:f59c
eno1: soliciting an IPv6 router
eno1: rebinding lease of 192.168.0.3
eno1: Router Advertisement from fe80::c23e:fff:fe2a:8b8c
eno1: adding address fda8:3e71:2eb6:0:3c02:829f:d71c:a8b9/64
eno1: adding address 2a02:c7d:25f3:2800:b8e1:f66c:e550:c1b3/64
eno1: adding route to fda8:3e71:2eb6::/64
eno1: adding route to 2a02:c7d:25f3:2800::/64
eno1: requesting DHCPv6 information
eno1: adding default route via fe80::c23e:fff:fe2a:8b8c
forked to background, child pid 14536 [ ok ]
* received address [ ok ]
[super] root@ad-gentoo-main / # * Starting openvpn ... [ ok ]
* WARNING: openvpn has started, but is inactive
* Mounting network filesystems ... [ ok ]
<RETURN PRESSED.>
[super] root@ad-gentoo-main / #

I suspect that this is just a silly bug in which a prompt is displayed
prematurely, and since the shell has already dispatched the $PS1, it waits
until <RETURN> is received before showing it again, as it thinks you're in the
process of typing a command. As the "Starting openvpn ..." text is printed to
stdout, when you press enter, it assumes an empty command has been entered and
does nothing but display another prompt.

As a simple demonstration, see what happens when I type a command `echo Hello`
before pressing enter:

[super] root@ad-gentoo-main / # etc/init.d/net.eno1 restart
<... TRIM OUTPUT ...>
[super] root@ad-gentoo-main / # * Starting openvpn ... [ ok ]
* WARNING: openvpn has started, but is inactive
* Mounting network filesystems ... [ ok ]
echo Hello
Hello
<RETURN PRESSED.>
[super] root@ad-gentoo-main / #

--

Ashley Dixon
suugaku.co.uk

2A9A 4117
DA96 D18A
8A7B B0D2
A30E BF25
F290 A8AA
Re: Strange output when restarting network. Long term issue. [ In reply to ]
Ashley Dixon wrote:
> On Wed, Jul 22, 2020 at 09:13:22PM -0500, Dale wrote:
>> See how it receives the address from the router and then gives a prompt
>> again, then it mounts network file systems where I should type in a
>> command but that isn't me..? To get a prompt again, I have to hit the
>> return key.? Why does it give me a prompt when it isn't done yet??
>> Shouldn't it finish completely before returning to a prompt?? This is in
>> a Konsole, within KDE.? That said, I'm pretty sure it does this on a
>> console, ctrl alt F*, screen as well.?
> I can confirm I get this also, using st (suckless/simple terminal). I have a VPN
> script in my net.eno1 script, so the output might differ slightly from yours,
> although the strange behaviour seems the same.
>
> [super] root@ad-gentoo-main / # etc/init.d/net.eno1 restart
> * Stopping openvpn ... [ ok ]
> * Unmounting network filesystems ... [ ok ]
> * Bringing down interface eno1
> * Stopping dhcpcd on eno1 ...
> sending signal TERM to pid 13839
> waiting for pid 13839 to exit [ ok ]
> * Bringing up interface eno1
> * dhcp ...
> * Running dhcpcd ...
> DUID 00:04:aa:aa:aa:aa:aa:aa:aa:aa:aa:aa:d8:cb:8a:c6:64:cd
> eno1: IAID 8a:c6:64:cd
> eno1: adding address fe80::fd5:dd1a:7c1c:f59c
> eno1: rebinding lease of 192.168.0.3
> eno1: carrier lost
> eno1: deleting address fe80::fd5:dd1a:7c1c:f59c
> eno1: carrier acquired
> eno1: IAID 8a:c6:64:cd
> eno1: adding address fe80::fd5:dd1a:7c1c:f59c
> eno1: soliciting an IPv6 router
> eno1: rebinding lease of 192.168.0.3
> eno1: Router Advertisement from fe80::c23e:fff:fe2a:8b8c
> eno1: adding address fda8:3e71:2eb6:0:3c02:829f:d71c:a8b9/64
> eno1: adding address 2a02:c7d:25f3:2800:b8e1:f66c:e550:c1b3/64
> eno1: adding route to fda8:3e71:2eb6::/64
> eno1: adding route to 2a02:c7d:25f3:2800::/64
> eno1: requesting DHCPv6 information
> eno1: adding default route via fe80::c23e:fff:fe2a:8b8c
> forked to background, child pid 14536 [ ok ]
> * received address [ ok ]
> [super] root@ad-gentoo-main / # * Starting openvpn ... [ ok ]
> * WARNING: openvpn has started, but is inactive
> * Mounting network filesystems ... [ ok ]
> <RETURN PRESSED.>
> [super] root@ad-gentoo-main / #
>
> I suspect that this is just a silly bug in which a prompt is displayed
> prematurely, and since the shell has already dispatched the $PS1, it waits
> until <RETURN> is received before showing it again, as it thinks you're in the
> process of typing a command. As the "Starting openvpn ..." text is printed to
> stdout, when you press enter, it assumes an empty command has been entered and
> does nothing but display another prompt.
>
> As a simple demonstration, see what happens when I type a command `echo Hello`
> before pressing enter:
>
> [super] root@ad-gentoo-main / # etc/init.d/net.eno1 restart
> <... TRIM OUTPUT ...>
> [super] root@ad-gentoo-main / # * Starting openvpn ... [ ok ]
> * WARNING: openvpn has started, but is inactive
> * Mounting network filesystems ... [ ok ]
> echo Hello
> Hello
> <RETURN PRESSED.>
> [super] root@ad-gentoo-main / #
>


At least it isn't just me.? Sometimes I think bugs/bad features pick on
me.? While annoying, I guess it is harmless.? It just seems that as long
as it has been doing this, someone would have raised the hood and looked
to see what is causing it and how to fix it.? Strange that something
weird like this has been around so long.?

Thanks for the reply.? At least I know I'm not alone.

Dale

:-)? :-)?
Re: Strange output when restarting network. Long term issue. [ In reply to ]
On Thu, Jul 23, 2020 at 08:46:52PM -0500, Dale wrote:
> At least it isn't just me.? Sometimes I think bugs/bad features pick on
> me.? While annoying, I guess it is harmless.? It just seems that as long
> as it has been doing this, someone would have raised the hood and looked
> to see what is causing it and how to fix it.? Strange that something
> weird like this has been around so long.?

I've just run it again, and it seems like the culprit is in the _show_address
function, which calls einfo [1], passing the result of _get_inet_address. I'll
have a look at this more now, as it's something I also would like to be
resolved.

--

Ashley Dixon
suugaku.co.uk

2A9A 4117
DA96 D18A
8A7B B0D2
A30E BF25
F290 A8AA
Re: Strange output when restarting network. Long term issue. [ In reply to ]
Ashley Dixon wrote:
> On Thu, Jul 23, 2020 at 08:46:52PM -0500, Dale wrote:
>> At least it isn't just me.? Sometimes I think bugs/bad features pick on
>> me.? While annoying, I guess it is harmless.? It just seems that as long
>> as it has been doing this, someone would have raised the hood and looked
>> to see what is causing it and how to fix it.? Strange that something
>> weird like this has been around so long.?
> I've just run it again, and it seems like the culprit is in the _show_address
> function, which calls einfo [1], passing the result of _get_inet_address. I'll
> have a look at this more now, as it's something I also would like to be
> resolved.
>


Thanks much.? Hopefully it is a easy fix.?

Dale

:-)? :-)?

Also tracking your euses package.? Got it installed but the patches are
giving me grief when I try to update.? Hopefully it will hit the tree
soon and be updated normally.?
Re: Strange output when restarting network. Long term issue. [ In reply to ]
Hello,

On Thu, 23 Jul 2020, Ashley Dixon wrote:
[..]
>[super] root@ad-gentoo-main / # etc/init.d/net.eno1 restart
[..]
>forked to background, child pid 14536
^^^^^^^^^^^^^^^^^^^^
[..]

It's just output from backgrounded processes. Just ignore it or enter
Ctrl-C to get a fresh prompt. Using enter is not recommended.

Compare running:

{ echo "start"; sleep 2; echo "done" ; } &

HTH,
-dnh

--
My word processor was written by Stanford Professor Donald Knuth. Who
wrote yours?
Re: Strange output when restarting network. Long term issue. [ In reply to ]
On Fri, Jul 24, 2020 at 02:59:10AM +0100, Ashley Dixon wrote:
> I've just run it again, and it seems like the culprit is in the _show_address
> function, which calls einfo [1], passing the result of _get_inet_address. I'll
> have a look at this more now, as it's something I also would like to be
> resolved.

It seems like this is not the case. This might be a bug in netifrc, or the
OpenRC init system helper functions in general. I can't find anything on-line
regarding this issue, although I'm sure it's reasonably common.

--

Ashley Dixon
suugaku.co.uk

2A9A 4117
DA96 D18A
8A7B B0D2
A30E BF25
F290 A8AA