[19:43] when should one add a system user? [22:35] Soni: only if you're adding a user that has no user interface or interaction and pretty much is only used for a system service [22:36] Soni: most of the time for daemons / services / things not run by a human user [22:36] ^^ [22:36] ah, so something that should only exist in the context of systemd units = system user [22:36] tomreyn: you and I both must be alive at the same hours lol [22:36] hehe [22:36] something we'll ssh into = non-system user? [22:36] Soni: pretty much yes [22:36] Soni: anything you SSH into is just a standard user [22:36] that was another funny coincident, teward [22:36] okay, that makes it easier [22:37] thanks! [22:37] Soni: 'system' class of users should be reserved soluely for daemons and services and things that don't get human interaction [22:37] yep [22:37] case in point we have a custom listserv system at a job. It operates on a SystemD timer under a system user called 'threader' [22:37] said 'threader' is existing for the program base and execution of it. Thank you SystemD :P [22:42] but that's a system user, no login shell, etc. [22:42] :) [22:42] Soni: glad that made it easier to understand, sorry about the delay of getting you a reply [22:42] (weekends are pretty dead xD) [22:42] tomreyn: you sure about that? :P [22:48] teward: if it wasn't a coincident, i must have been sitting just next to my enter key, watching the channel patiently for someone to respond, finally allowing me to send that pre-composed message. [22:48] lol [22:49] you might characterize me as a little weird, but not that much. ;-) [22:49] in terms of 'weird' i'm pretty high up on that scale :P [22:49] so i mean [22:49] or maybe we're really just one person with two identities. [22:50] anyways, it was good chatting to the other side for a while. ;-) [23:08] lol [23:08] tomreyn: well i am in the shadows 24/7/365 so yeah 'the other side' xD [23:08] in either case, alls good :) === vlm_ is now known as vlm