title: How to stop systemd from spamming rsyslog in CentOS 7
body: <p>I've followed the instructions in this <a href="https://bugzilla.redhat.com/show_bug.cgi?id=727315" rel="nofollow">Redhat Bugfix article</a>, that is I did the following (I realize this is a Redhat fix)</p>
  
  <ul>
  <li>Create a /etc/systemd/system/systemd-logind.service file</li>
  <li><p>put the following lines in the file</p>
  
  <p>.include /lib/systemd/system/systemd-logind.service
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=warning</p></li>
  <li><p>Restarted the rsyslog and systemd-logind services</p></li>
  </ul>
  
  <p>Yet I still see systemd logs spamming /var/log/messages. Anything else I need to do in a CentOS box? Here's a sample</p>
  
  <pre><code>&lt;30&gt;1 2016-08-23T13:09:48-04:00 susralcent09 systemd - - -  Starting Flush Journal to Persistent Storage...
  &lt;30&gt;1 2016-08-23T12:48:37-04:00 susralcent09 systemd - - -  Started System Logging Service.
  &lt;30&gt;1 2016-08-23T12:48:36-04:00 susralcent09 systemd - - -  Stopping System Logging Service...
  &lt;30&gt;1 2016-08-23T12:48:36-04:00 susralcent09 systemd - - -  Starting System Logging Service...
  </code></pre>
  
  <p>...and</p>
  
  <pre><code>&lt;30&gt;1 2016-08-23T13:01:01-04:00 susralcent09 systemd - - -  Created slice user-0.slice.
  &lt;30&gt;1 2016-08-23T13:01:01-04:00 susralcent09 systemd - - -  Started Session 2 of user root.
  &lt;30&gt;1 2016-08-23T13:09:48-04:00 susralcent09 systemd - - -  Started Flush Journal to Persistent Storage.
  &lt;30&gt;1 2016-08-23T13:01:01-04:00 susralcent09 systemd - - -  Starting Session 2 of user root.
  &lt;30&gt;1 2016-08-23T13:01:01-04:00 susralcent09 systemd - - -  Starting user-0.slice.
  </code></pre>