<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: User Errors &#8211; the bane of the techie&#8217;s existence</title>
	<atom:link href="http://g33q.co.za/2008/07/06/user-errors-the-bane-of-the-techies-existence/feed/" rel="self" type="application/rss+xml" />
	<link>http://g33q.co.za/2008/07/06/user-errors-the-bane-of-the-techies-existence/</link>
	<description>The New Look Tech Blog</description>
	<lastBuildDate>Tue, 15 May 2012 17:00:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jaco</title>
		<link>http://g33q.co.za/2008/07/06/user-errors-the-bane-of-the-techies-existence/comment-page-1/#comment-75</link>
		<dc:creator>Jaco</dc:creator>
		<pubDate>Sun, 06 Jul 2008 20:11:01 +0000</pubDate>
		<guid isPermaLink="false">http://tech.blat.co.za/2008/07/06/user-errors-the-bane-of-the-techies-existence/#comment-75</guid>
		<description>Hehe, yes.  The STU was rather problematic.  In fact, rather frustrating.  To say the least.  The NINNIE problem extends further than that though.

Take the fact that we did in fact create two separate user groups.  And already someone (yes, the STU is the primary suspect) created a &#039;staff&#039; user with unlimited access and gave those credentials to students for their use. *sigh*.  You may not be a BOFH - but I can be.  Lecturers loved (and hated) me for that very reason.  I was known for revoking privileges when abuse was found, or disabling user accounts, and even (in one particular case) suspected compromise of an account could evoke rather severe reaction.  I did calm quite significantly from those days but as many of my posts on the GLUG list can attest to - it&#039;s still in me.  I was actually quite surprised that you didn&#039;t just disable the user1 account.

As for empowering the people - I fully agree.  You cannot babysit people all the way.  You prod them in the right direction and then leave them.  If you&#039;re their boss ... some additional prodding may be required from time to time.  And eventually the cattle-prod may need to come out.</description>
		<content:encoded><![CDATA[<p>Hehe, yes.  The STU was rather problematic.  In fact, rather frustrating.  To say the least.  The NINNIE problem extends further than that though.</p>
<p>Take the fact that we did in fact create two separate user groups.  And already someone (yes, the STU is the primary suspect) created a &#8217;staff&#8217; user with unlimited access and gave those credentials to students for their use. *sigh*.  You may not be a BOFH &#8211; but I can be.  Lecturers loved (and hated) me for that very reason.  I was known for revoking privileges when abuse was found, or disabling user accounts, and even (in one particular case) suspected compromise of an account could evoke rather severe reaction.  I did calm quite significantly from those days but as many of my posts on the GLUG list can attest to &#8211; it&#8217;s still in me.  I was actually quite surprised that you didn&#8217;t just disable the user1 account.</p>
<p>As for empowering the people &#8211; I fully agree.  You cannot babysit people all the way.  You prod them in the right direction and then leave them.  If you&#8217;re their boss &#8230; some additional prodding may be required from time to time.  And eventually the cattle-prod may need to come out.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

