On 15/12/15 22:01, David Lang wrote:
Also, with the upstart config changes, you want to do service rsyslog stop; service rsyslog start, not service rsyslog restart (and you may actually need to reboot, I don't remember) to make sure the new version of the file is in effect.
Good Lord, really? I did not know that. I was indeed using "restart rsyslog". My hack that worked did so by modifying a file that was sourced by the upstart .conf file, while modifying the .conf file appeared to have no effect. If upstart was simply not reloading the .conf file then that would explain everything! I'll investigate further and report back.
All the best, Giles -- Giles Thomas <[email protected]> PythonAnywhere: Develop and host Python from your browser <https://www.pythonanywhere.com/> A product from PythonAnywhere LLP 17a Clerkenwell Road, London EC1M 5RD, UK VAT No.: GB 893 5643 79 Registered in England and Wales as company number OC378414. Registered address: 28 Ely Place, 3rd Floor, London EC1N 6TD, UK _______________________________________________ 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.
