public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Strange output when restarting network. Long term issue.
Date: Wed, 22 Jul 2020 21:13:22 -0500	[thread overview]
Message-ID: <0efa1b11-c12c-3554-1f64-18a16f8492f2@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3358 bytes --]

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

:-)  :-) 

[-- Attachment #2: Type: text/html, Size: 3891 bytes --]

             reply	other threads:[~2020-07-23  2:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23  2:13 Dale [this message]
2020-07-23  4:46 ` [gentoo-user] Strange output when restarting network. Long term issue Ashley Dixon
2020-07-24  1:46   ` Dale
2020-07-24  1:59     ` Ashley Dixon
2020-07-24  2:14       ` Dale
2020-07-24  2:52       ` Ashley Dixon
2020-07-24  2:33   ` David Haller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0efa1b11-c12c-3554-1f64-18a16f8492f2@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox