Summary: | Syslog-ng starts too long when net.* scripts are using for network | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sergey Torokhov <torokhov-s-a> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sergey Torokhov
2016-06-09 07:36:21 UTC
The problem seems to be resolved by adding "127.0.0.2 MYHOSTNAME.domain MYHOSTNAME" string to the file "/etc/hosts". Now systemlog-ng doesn't prevent a quick boot of system. Where "MYHOSTNAME" is the hostname of my virtualbox gentoo machine. Is it obligatory to have any mentions of current hostname in "/etc/hosts" file while setting up the network? The more correct solution is that using syslog-ng with "net.*" scripts requires initial setting up of "/etc/hosts" file as described in the handbook: https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/System#The_hosts_file something like: # This defines the current system and must be set 127.0.0.1 tux.homenetwork tux localhost ::1 tux.homenetwork tux localhost where "tux" is the hostname that used in /etc/cond.f/hostname (hostname="tux") P.S. Also this initial setting up is required for successful starting of xorg-server by "startx" command. There is no information about it in https://wiki.gentoo.org/wiki/Xorg/Guide). Maybe some handbook and wiki editing may be helpful to clarify that network configuring and especially of "/etc/hosts" is necessary to correct working of such service as System Logging and Xorg-Server. |