On 11/7/2017 12:25 PM, deoren wrote:
On 11/7/2017 10:31 AM, matthew.gaetano wrote:
With the exception of the relation to storage, yes, for the most part. We
encountered the issue on a physical server using SCSI/SATA drives. Our
secondary tester were in vmware.
I initially emphasized the boot speed from running the Ubuntu 16.04 VM
on a SSD, but I believe the problem is mainly to do with the startup
ordering of rsyslog and network support. I ended up working around the
issue of rsyslog starting before network support was available by
modifying the systemd unit with a conf fragment:
# /etc/systemd/system/rsyslog.service.d/10-wait-on-network.conf
[Unit]
After=network.target
It mostly works for us and appears to be what stock CentOS 7 is doing
with their rsyslog package.
I went back and was unable to find an example where a distro-provided
package is setting 'After=network.target' in the '[Unit]' section of a
rsyslog.service or syslog.service unit file.
I'm sure I saw it somewhere, but checking these distros/versions I
didn't spot it:
* Debian 8, 9
* RHEL 7
* CentOS 7
* Ubuntu 16.04
I'll keep looking.
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
