Thread-topic: the joys of macintosh administration
User-agent: Microsoft-Entourage/12.0.0.071130
On 3/26/08 4:02 PM, "Jerry L. Blackmon II" <email@hidden>
wrote:
> On Mar 26, 2008, at 2:54 PM, Paul Teeter wrote:
>
>> Not sure, but it had MANY capital letters.
>
> Sorry, I forgot Open Directory and iCal Server were regular Mac OS X _client_
> technologies. My bad. User account management? Not at all related to a
> server, no sir. Of course, a quick read of the subject line of the e-mail
> might have clarified all, but that seems to be beyond the cognitive capacities
> of the Blame the User(TM) coterie that makes all us systems administrators
> look like cave dwelling trolls.
My comment was simple. Please don't SHOUT when you email the list. We get
it, you're exasperated.
> On Mar 26, 2008, at 5:57 PM, Dan Shoop wrote:
>
>> If you care to post issues and are interested purely in pursuing solutions
>> than I'd suggest you take that tack. However, as John noted, I see nothing
>> problematic other than the issues you've created for yourself.
>
> Problems I've created myself? Oh, that's good to know. Let's see which of
> these problems were created by my hand, since problems of my creation are by
> definition problems I can fix. User password corruption. Yeah, that's
> definitely one of mine. Let me just run my handy-dandy uncorrupt utility to
> take care of that. Sorry for troubling you. Directory services setup?
> That's right, let me consult the inscrutable documentation, fire up the
> command line and do it by hand. It'll take a bit longer, but it won't cause
> the problems created by using the utility that I somehow mistakenly believed
> would configure the system in a way that didn't cause me additional problems
> after running it. Command line is definitely the way to go. Logging into
I'm going to hazard the assumption that denigrating the command line as you
appear to be doing is not going to win you many friends here.
While I agree that Directory Utility can and often does 'just work', the
dsconfigldap (dsconfigad) tool is often far more verbose when directory
binding fails. Furthermore, quite often the command line is the only or at
least most convenient way to, oh I don't know, restart a service in debug
mode so it will log the errors you are seeing with more detail.
True, Console will work for viewing such logs. I just like tail more, call
me a cave dwelling troll.
> user accounts? Yeah, command line again. It doesn't give you the user
> environment so you can set preferences within programs, but who needs to do
> that right? iCal errors. Let me read the documentation. There is none? Oh
> I know, I'll just use Entourage! That's the ticket.
>
> So again, where are these problems I've supposedly created for myself? I mean
> besides the decision I made to use Apple technology because it's supposed to,
> you know, just work. As with more than a few of the posts on this list, I've
> found, yours is long on snark and short on beef; I've seen your mouth and know
> where it is, but sadly you've put no money there. Perhaps you should have
> dropped this one in /dev/null before you wasted time sending it.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden
This email sent to email@hidden
