Using my psychic powers, I predict your old box didn't have a dash anywhere within the hostname, but the new one does.
Do I win the prize?
The dashes are just delimiters, but you have to be careful as to what uname -n returns.
-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply. | [reply] |
You have just won a shiney, slightly used, half full, styrofoam coffee cup!!!
"Nothing is sure but death and taxes" I say combine the two and its death to all taxes!
| [reply] |
Not going into the fact that there are probably a lot of ways to do this differently (this way, you are launching three processes to do a simple substition in a file), I hazard a guess that `uname -n` is returning a string that contains a dash, whereas it did not before. Unfortunately, if that's the problem, you are pretty much obliged to change the scripts...
CU Robartes- | [reply] |
Personally, I'd go ahead and make sure every hostname on my network didn't have a '-', then make that a requirement for anyone using my ...
Ooops. Wrong forum. I thought I was on Evilmonks.
------ We are the carpenters and bricklayers of the Information Age. Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.
| [reply] |
Heh, not really. Since the machine is mine, I just change the hostname :)
"Nothing is sure but death and taxes" I say combine the two and its death to all taxes!
| [reply] |
tye called this one right, the command uname -n returned a value with a - char in it...hence my problem.
"Nothing is sure but death and taxes" I say combine the two and its death to all taxes! | [reply] [d/l] |