Leo: This doesn't help your ssh issue, and I know this is probably
very bad practice, but because of the problem we've been having it's
worth it. I leave myself logged on via ssh, in a root shell. At the
very least it allows me to re-boot the server when things go bad, or
start going bad. I generally leave the shell running "top -o cpu",
and I can see when things are about to go belly up. ANYTHING that
requires looking up ANY info stored in the directory will fail.
There is very little you can do at that point...
ALL: So, is there anyone out there that can help on the original
topic of this thread? Any ideas about how to work out what might be
happening? Any ideas on how to log it, spot it, track it, trace it,
fix it? Anything !!!
David Minard.
Ph: 0247 360 155
Fax: 0247 360 770
School of Computing & Mathematics
Building Y - Penrith Campus (Kingswood)
Locked bag 1797
Penrith South DC
NSW 1797
[Sometimes waking up just isn't worth the insult of the day to come.]
On 30/10/2007, at 6:08 AM, Leo R. Lundgren wrote:
29 okt 2007 kl. 19.52 skrev Dan Shoop:
On Oct 29, 2007, at 2:40 PM, Leo R. Lundgren wrote:
I know you didn't post that to the list, but your message at
least looked like it could contribute to the discussion, therefor
I posted it to the list.
If you want laundry in public, so be it...
Dan,
If you see something in the log I posted, why not tell us what it
is instead of slipping off the subject once again. The fact that
you so often just go around telling people that there could be
another problem and that one should read every ounce of
documentation available to the world, is what I think pisses some
people off.
Yes, like being called a fool.
I may be a curmudgeon but I don't specifically call people names
on mailing lists.
Moreover doing so hardly is inviting to others to assist you.
Sure, sometimes it's good to point out that one shouldn't ask
questions without any research or logical thought behind it. But
you still have to remember that there are a lot of people out
there that try their best to keep a small business running, and
many of us simply don't have the time/resources to read up on
everything.
Right, so it's better to have others do your work for free. Just b/
c your resources may be limited doesn't mean you can frob off your
work onto others.
Look, I do a lot of helping on the net as well, so whatever help
I'm asking it's surely not being asked without giving anything back
to the community as a whole. Also, if I can help someone who needs
it even if they can't give anything but a "thank you" back, I do it
if I have a minute to spare. Thinking that they just frob off of my
work won't help anyone in the long run.
Anyhow, it would be great if you could do more into detail about
the SSH logs I posted.
Right, you've made it so appealing to help you.
Is there anything in there showing why I can't connect via SSH
when DirectoryServices are down, while it works great when they
aren't?
I'm sorry, I'm a fool, remember? So anything I say would, I
suppose, be foolishness; however obvious it may be.
I do not consider you a fool, lol. Not everything is constant you
know.
-|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40scm.uws.edu.au
This email sent to email@hidden
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
