So i desperately need help finding the system wide settings file for KScreensaver. I need to find this file to enable screensaver and screen lock for new users. I thought the /usr/share/config.kcfg/kscrreensaver.kcfg would be the right file, but when i wipe out my .kde file in my home directory it just creates a new screensaverrc with the original defualts that came with my version.

Im Using
SL6
KDE4

Please help

you could work with the new users' ~/.kde[4]/share/config/kscreensaverrc by replacing it with a root owned link to a communal rc file that they only have read access to

Not a bad idea, I'll take a look at how feasible that is, but id still like to find the file that the RC is created from, and make the changes there

if you find and make the change on the file the RC is created from you would sill want to make it read only I would assume

Not necessarily, users still need to be able to have the option to disable the screensaver/screenlock if they are going to be making a presentation or something. But that only pertains to the rc.

I realize this sounds slightly silly to enforce something and still offer users the ability to change it back. but that's what i need to do

you could consider caffeine, a tray app that disables powersave for a period of time or for particular apps https://launchpad.net/caffeine. installed fine but have not tested (dl'ed the tar and ran the python script in the bin sub-directory).

maybe ask how to disable the screen saver when in full screen mode

Hmm think weve moved to two different wave lenghs here.
I need the screensaver enabled. And using another app to effect settings in my screensaver is a lil silly. But thanks though.

It's hard to believe that no ones dealt with this before, sense having screensaver\screenlock by default is a very common security requirement. And being able to edit one file for the global settings, instead of per session, is a must as an admin.

The kscreensaverrc file will have been drawn from the KDE Global configuration directory. Where this is located is dependent on your distribution unfortunately. You can use immutable settings to prevent users from changing the preferences if you want - this is part of the Kiosk framework.