Finally got it to work. There were 2 problems:
I did need to change the firewall setting in Fedora to open the port (thanks).
The other issue was that under Fedora, q displays the loopback inet address, which does not work for interprocess communication.
I needed to use the ifconfig command while logged in as root to determine the correct inet address.
Thanks again.
You can list the interface information without su:ing to root; youjust need to prefix the command with the full path since the locationisn’t in a normal user’s PATH variable, like so:/sbin/ifconfig..just my $0.01 worth.
Thanks. I tried it, and it works on my machine too.
Actually, it seems like pretty quirky stuff to me:
I originally tried su:ing to root.
did not work, and still doesn’t.
I logged out as an unprivileged user and logged in as root. Then
did work.
However,
works both as an unprivileged user and when su:ing.
Apparently the PATH variable is not affected by su:ing.
As in most things, the devil lies in the details:When calling su, including the “-” option will make the shell youobtain as the other user (root is default when call su without ausername argument) be a login shell.This means that various configuration files for the other user’s shellis read, setting the PATH variable as expected (among other things).If the “-” argument is left out, the PATH variable (among others) isare inherited from the user you are su:ing from.Example calls:# Change user to root, inherit settings from the user being su:d fromsu# Change user to root, make the shell obtained after su a login shellsu -# Change to user foobar, make the shell obtained after su a loginshellsu - foobar
Great stuff. Thanks.