On Sun, 18 Oct 1998 [EMAIL PROTECTED] wrote:
> Michael Beattie writes:
> > I imagine you have no NIC? If so, then for people that do, probably dont
> > need to do this. e.g.:
>
> No Sir, I do have a NIC installed. I'm using an unrouted address (192.168.x.x)
> And diald was doing the dirty deed 8-
Michael Beattie writes:
> I imagine you have no NIC? If so, then for people that do, probably dont
> need to do this. e.g.:
No Sir, I do have a NIC installed. I'm using an unrouted address (192.168.x.x)
And diald was doing the dirty deed 8-) inspite of the additional information
in my /etc/hosts f
On Sat, 17 Oct 1998 [EMAIL PROTECTED] wrote:
> 1) edit the /etc/hosts file and add your hostname behind the 'localhost'
> example:
> old '/etc/hosts'
> 127.0.0.1 localhost
>
> new '/etc/hosts'
> 127.0.0.1 localhost westgac3 << use the name returned by 'hostname'
>
I imagine you have no
Thomas Kocourek writes:
> 2) Then reboot your system.
No need to reboot.
--
John HaslerThis posting is in the public domain.
[EMAIL PROTECTED] Do with it what you will.
Dancing Horse Hill Make money from it if you can; I don't mind.
Elmwood, Wisconsin
I asked on the list if anyone could tell me how to find what process was
connecting to a socket. lsof looked promising but did not work as advertised
in it's documentation. However, I did some detective work and found that
"diald" was the culprit. Here's how it happens:
diald is started by the ini
5 matches
Mail list logo
