by DThor (Posted Sat, 13 Jul 2013 18:51:10 GMT)
This isn't really a fix, it's a workaround for files that are being stored in the wrong location, with the wrong permissions. If you install a clean newsbin and use default locations, this will never happen, but it is common for users to be upgrading at some point from a non-UAC version of windows, like XP, to win7. They'll often carry over non UAC friendly locations for configuration files, and running newsbin as administrator gives them permission to overwrite locations they 'shouldn't' as an end user.
I'm not saying you've done something horrifically wrong, it's your computer, just wanted to point out for others that running newsbin as root isn't a good idea, and if it makes something broken fixed, then it's an indication of something set up incorrectly. Lots of people do it, but it's an end runaround system security.
It's a little unclear if it's related to the fix, however, since you changed two things at once by deleting your groups.db3.
DT
Read Main Topic
This isn't really a fix, it's a workaround for files that are being stored in the wrong location, with the wrong permissions. If you install a clean newsbin and use default locations, this will never happen, but it is common for users to be upgrading at some point from a non-UAC version of windows, like XP, to win7. They'll often carry over non UAC friendly locations for configuration files, and running newsbin as administrator gives them permission to overwrite locations they 'shouldn't' as an end user.
I'm not saying you've done something horrifically wrong, it's your computer, just wanted to point out for others that running newsbin as root isn't a good idea, and if it makes something broken fixed, then it's an indication of something set up incorrectly. Lots of people do it, but it's an end runaround system security.
It's a little unclear if it's related to the fix, however, since you changed two things at once by deleting your groups.db3.
DT
Read Main Topic