© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
At first glance, I suspect the simplest fix here is to check if the syslog user exists, before attempting to change ownership, and if that user does not exist, do nothing, assuming the local administrator handled it already in some other way.