[03:25] <Takyoji> We really need to throw together an initiative of people being active in support channels. Pretty much all the FOSS support channels are filled with people, but nobody ever helps/answers.
[03:26] <tonyyarusso> Or they answer incorrectly :P
[03:28] <Takyoji> right now I'm looking for a way to disable 'switch users' option, so that user sessions don't pile up, but I'm under the impression that it would be set in a user's .gconf folder, but then that would mean they can remove it. Is there a way to disable it system-wide and not have users be able to remove the enforcement?
[03:28] <Takyoji> Also, I found that it is desktop/gnome/lockdown/disable_user_switching which dictates such
[03:28] <Takyoji> I've asked on various channels, even the official GNOME channel, no answers.
[03:28] <tonyyarusso> Is there a system-wide version of the same key?  Can that tool - sabayon maybe - do it?
[03:29] <Takyoji> I'm under the impression that there's also a gconf registry in /etc or similar that's supposed to be system-wide and I think you can enforce certain values as 'mandatory', but I don't know how to go about that.
[03:30] <Takyoji> in a way that I can do it via command line on several systems via SSH
[03:30] <tonyyarusso> /etc/gconf/gconf.xml.mandatory looks promising
[03:32] <tonyyarusso> You can probably use gconftool with the --config-source option to use that
[03:33] <tonyyarusso> Takyoji: does that help?
[03:33] <Takyoji> I believe so
[03:34] <Takyoji> I've concocted: gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type bool --set /desktop/gnome/lockdown/disable_user_switching true
[03:34] <tonyyarusso> seems plausible
[03:35] <Takyoji> Next I wonder how one can remotely set the default email client. :P
[03:35] <Takyoji> I srsly should document all the things I find through this process of remote sysadmin through SSH
[03:36] <Takyoji> I say, I could certainly become an LPIC-3 faster than ye. :P
[03:37] <tonyyarusso> lol
[03:38] <Takyoji> Have you set up Evolution for a whole network of users using only commandline, and setup network printers, and so on (all via command line)? :P
[03:39] <tonyyarusso> Sadly I've never had a need to.
[03:39] <Takyoji> of course I could do all this in person, but that means a $72 drive there
[03:40] <Takyoji> (just from gas and car wear)
[03:40] <Takyoji> in-person*
[20:13] <tonyyarusso> Hey Takyoji - you know how you were talking about managing labs and things?  Could you document the hell out of what you know and send it to me?  There's someone at work who wants to do a presentation about managing Linux labs for school environments, so that would be handy for him to have.
[20:15] <Takyoji> Right now I'm sort of doing things by hand, as of things on a per-workstation basis (I don't have puppet or anything setup for deployment)
[20:15] <Takyoji> But yes, I can document all the details of the setup, as there is some witty automation that I have for it all
[20:24] <tonyyarusso> Even just your scripting stuff is fine.
[22:49] <rlaager> tonyyarusso: A Google search found this: http://http://www.eyrie.org/~eagle/notes/debian/server.html
[22:49] <rlaager> The Debian packaging outlined therein is more or less what I'm doing. I'm not using Puppet at all. Now, I'm dealing with servers, not lab workstations, so this isn't perfectly applicable to what you're asking.
[22:50] <rlaager> We work with a K12 school and used CloneZilla to image their Windows lab computers.