Nick Howitt wrote:
So who is user 1000? Are you using "useradd" to add your tsdaemon user? If so you must use the -r switch to create it as a system user. If you don't, it will end up in the space controlled by LDAP and get wiped on every reboot.
That's a good question, and one I had too, I'm not sure who user 1000 is, it's definitely not one I had created, I assumed it was some sort of system account. That's a bit concerning.
When I created the account I did not use the -r switch. I did get this issue working last night though by using the -R switch on my chown command. Using that I was able to go in and start the server with that script, and pull tsdaemon out of the sudoers file. However, and this may play into what you're saying with the system user, I attempted to reboot the server this morning, and when it came back up it doesn't look like the cron job worked. I was still able to use su tsdaemon, and get to my home directory to manually launch the script/server again, but the cron job didn't pick it up. Would that be caused by not having used that -r switch?