I have a weird problem.
526 hostname
saturn.syslang.net
527
But, ...
527 perl -MNet::Domain -e 'print Net::Domain::hostfqdn(), \n'
saturn.com
527 perl -MNet::Domain -e 'print Net::Domain::hostdomain(), \n'
com
528 perl -MNet::Domain -e 'print Net::Domain::hostname(), \n'
saturn
And it
On 2/18/06, Paul Lussier [EMAIL PROTECTED] wrote:
That means they're in uninterruptable sleep ... Bad hardware or
buggy device drivers are the most common cause of a process
stuck in this state.
Or, an NFS server from which this system mounted a file system has
gone off the net.
Oh, yah,
On 2/19/06, Steven W. Orr [EMAIL PROTECTED] wrote:
526 hostname
saturn.syslang.net
527
[cut[
You might also try these:
hostname -f
hostname -s
hostname -d
hostname -a
hostname -i
And it takes almost 30 seconds to come back.
Hmmm. Smells like a DNS problem. Try doing forward and
On 2/19/06, Steven W. Orr [EMAIL PROTECTED] wrote:
526 hostname
saturn.syslang.net
When setting my system's hostname, I *prefer* (emphasis indicates a
subjective opinion) to set the system's hostname to the short
(unqualified) name. For example:
$ hostname
wildfire
Then, I
Short version: Apple builds DRM (Digital Restrictions Management)
into MacOS-for-x86 to prevent it from running on non-Apple hardware.
DRM gets cracked. Apple fan forum sites links to info on crack. Just
*links*, mind you. In response, Apple's fires DMCA missles at the
forums in question.
On Sunday, Feb 19th 2006 at 17:17 -0500, quoth Ben Scott:
=On 2/19/06, Steven W. Orr [EMAIL PROTECTED] wrote:
= 526 hostname
= saturn.syslang.net
= 527
=[cut[
=
= You might also try these:
=
=hostname -f
=hostname -s
=hostname -d
=hostname -a
=hostname -i
I made the change you suggested below
On Sunday, Feb 19th 2006 at 17:17 -0500, quoth Ben Scott:
=On 2/19/06, Steven W. Orr [EMAIL PROTECTED] wrote:
= 526 hostname
= saturn.syslang.net
= Also, make sure your /etc/resolv.conf file includes syslang.net as
=one of the search domains.
One more thing: I get my resolv.conf from rcn via
Bill McGonigle [EMAIL PROTECTED] writes:
On Feb 18, 2006, at 21:26, Paul Lussier wrote:
One that's done,
configure the NIC to use the exact same IP as the NFS server which
suddenly disappeared.
Did you try to bring up a virtual interface on the problem machine
with the original server's
On 2/19/06, Paul Lussier [EMAIL PROTECTED] wrote:
Won't mounting the NFS filesystems with the soft,intr options
prevent that from happening in the first place?
If you have the O'Reilly book for NFS and NIS ...
Let's assume I don't. Please explain.
In the past, when working with NFS,
On Sun, 19 Feb 2006 19:45:19 -0500, Ben Scott wrote:
What's the fix for when Red Hat derived systems (in the current
case, my Fedora Core 4 desktop) display crap in man pages?
[Suggestion of dumping FC for $OTHERDISTRO reconsidered and omitted.]
This typically manifests as a highlighted
I have a devious, wave-the-dead-chicken voodoo hack that
will sometimes save the day when you're suffering the dread
Stale NFS file handle error. It only unwedges NFS clients,
and only sometimes, but when you're foaming at the mouth with
frustration it's a good trick to know. ( Hey, Paul - you
On 2/19/06, Steven W. Orr [EMAIL PROTECTED] wrote:
I made the change you suggested below to the hosts file.
[output from hostname commands cut]
Okay, all of those look good. Did any of those hostname commands
include a 30 second pause?
[EMAIL PROTECTED] etc]# host saturn.syslang.net
Ben Scott wrote:
For example, it was recently pointed out to me that, for the case of
a 2LD has only one server, and that server handles only that
domain, setting the system hostname to the 2LD means one does not
have to configure certain other things to know the difference between
the
Michael ODonnell [EMAIL PROTECTED] writes:
The following explanation is presented from my perspective where
I'm trying to regain access to my NFS mounted home directory
but should be applicable in other contexts if you tweak the
appropriate things:
ASSUME:
- Home directory resides
Ben Scott [EMAIL PROTECTED] writes:
What's the fix for when Red Hat derived systems (in the current
case, my Fedora Core 4 desktop) display crap in man pages?
Fire up emacs, and either:
M-x manRETname of commandRET
or:
C-h i
to enter info mode, which the Gnu people seem to feel is
On 2/19/06, Bill Mullen [EMAIL PROTECTED] wrote:
What's the fix for when Red Hat derived systems (in the current
case, my Fedora Core 4 desktop) display crap in man pages?
[Suggestion of dumping FC for $OTHERDISTRO reconsidered and omitted.]
Avoiding controversy and debate? Come now.
On 2/19/06, Paul Lussier [EMAIL PROTECTED] wrote:
What's the fix for when Red Hat derived systems (in the current
case, my Fedora Core 4 desktop) display crap in man pages?
Fire up emacs, and either:
M-x manRETname of commandRET
Just FYI, that didn't fix anything, either. Neener,
Can you explain *why* this works?
Nope.
P.S. in case that smiley I included wasn't clear enough I
should mention that (best we could determine) it was a
nasty kernel NFS bug that was giving us fits at the time
and nothing we could blame on Paul, try as we might!
18 matches
Mail list logo