Hugo Chavez? (He is dead) Any other (in)famous Hugos out there?
On Thu, Jan 9, 2025, 15:34 Russell Senior <[email protected]> wrote: > Another command is: > > lsof -P -iTCP -sTCP:LISTEN > > The -P option causes lsof to not convert port numbers into port names, > so you can see the actual port number, the other options restricts > lsof to reporting TCP ports in LISTEN state. The lsof command will > tell you which process is listening on which ports. > > I don't know what Hugo is, but to "add" it, you need to tell Hugo to > listen on that port. Since I don't know what Hugo is, I don't know how > to tell it what port to listen to, or even if it is designed to listen > to any ports. > > -- > Russell Senior > [email protected] > > On Thu, Jan 9, 2025 at 12:18 PM Rich Shepard <[email protected]> > wrote: > > > > On Thu, 9 Jan 2025, Russell Senior wrote: > > > > > Try: > > > netstat -tan | grep LISTEN > > > > $ netstat -tan | grep LISTEN > > tcp 0 0 127.0.0.1:8118 0.0.0.0:* > LISTEN > > tcp 0 0 0.0.0.0:631 0.0.0.0:* > LISTEN > > tcp 0 0 127.0.0.1:5432 0.0.0.0:* > LISTEN > > tcp 0 0 0.0.0.0:25 0.0.0.0:* > LISTEN > > tcp 0 0 127.0.0.1:2812 0.0.0.0:* > LISTEN > > tcp 0 0 0.0.0.0:37 0.0.0.0:* > LISTEN > > tcp 0 0 0.0.0.0:14982 0.0.0.0:* > LISTEN > > tcp 0 0 127.0.0.1:783 0.0.0.0:* > LISTEN > > tcp 0 0 0.0.0.0:80 0.0.0.0:* > LISTEN > > tcp 0 0 0.0.0.0:113 0.0.0.0:* > LISTEN > > tcp6 0 0 :::631 :::* > LISTEN > > tcp6 0 0 :::14982 :::* > LISTEN > > tcp6 0 0 ::1:783 :::* > LISTEN > > > > > If you see the ports you expect, then start to consider whether > > > localhost is resolving. The usual place for that to happen is in > > > /etc/hosts. On my system, I see something like this in /etc/hosts: > > > 127.0.0.1 localhost.localdomain localhost > > > > 127.0.0.1 localhost.localdomain localhost > > > > How do I add 127.0.0.1:1313? That's where Hugo lets me see my local > website. > > > > Thanks, Russell, > > > > Rich >
