Re: [DNG] who's tying up my port 80?
On Wed, 11 Jul 2018 00:27:17 +0200 Harald Arnesen wrote: > Rowland Penny [2018-07-10 15:44]: > > On Tue, 10 Jul 2018 15:36:46 +0200 > > Harald Arnesen wrote: > > > >> Rowland Penny [2018-07-10 14:37]: > >> > >> > The problem is that it is probably easier to start anew rather > >> > than trying to update/maintain an existing project. You have to > >> > contact the existing maintainer (and you could have problems > >> > actually finding the maintainer), get their permission to update > >> > the package or fix bugs and then do what you wanted to do in the > >> > first place. > >> > >> Get their permission? Aren't we using free software? > > > > If you want to update a packages code, you need to get at it, > > otherwise it is called a fork, therefore you need the maintainers > > permission to change it. > > If you can't get hold of the maintainer? Then I suppose it depends on whether you can obtain the source code. If you cannot, then you cannot do anything, if you can, then you will probably have to fork it. Rowland ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
Rowland Penny [2018-07-10 15:44]: > On Tue, 10 Jul 2018 15:36:46 +0200 > Harald Arnesen wrote: > >> Rowland Penny [2018-07-10 14:37]: >> >> > The problem is that it is probably easier to start anew rather than >> > trying to update/maintain an existing project. You have to contact >> > the existing maintainer (and you could have problems actually >> > finding the maintainer), get their permission to update the package >> > or fix bugs and then do what you wanted to do in the first place. >> >> Get their permission? Aren't we using free software? > > If you want to update a packages code, you need to get at it, otherwise > it is called a fork, therefore you need the maintainers permission to > change it. If you can't get hold of the maintainer? -- Hilsen Harald ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
Quoting KatolaZ (kato...@freaknet.org): > Yeah, I knew the link, and it correctly says that net-tools has not > seen a new release since 2011 (which is 7 years, not 17 :P). > > And thanks a lot for the link. This is the way a discussion should go > :) Yr. very welcome! On the arithmetic error, I plead caffeine underflow error. ;-> > Rick, thanks again for this other link: I will go through the thread, > promise, and I am sure I will learn something useful. My whole point > was that old does not necessarily mean bad (which seems to have become > fancy these days) or gold (which is another dangerous tenet). With which I heartily agree. I'll also admit that I grumbled mightily about ceasing to use nslookup, because, essentially, just decades of familiarity. Downright cranky I was about needing to learn 'dig'. But the latter's advantages were compelling, even before you stopped to consider nslookup's queasy-making use of antique BIND 4.x spaghetti code. -- Cheers, "I am a member of a civilization (IAAMOAC). Step back Rick Moenfrom anger. Study how awful our ancestors had it, yet r...@linuxmafia.com they struggled to get you here. Repay them by appreciating McQ! (4x80) the civilization you inherited." -- David Brin ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
On Tue, Jul 10, 2018 at 09:41:11AM -0700, Rick Moen wrote: > Quoting KatolaZ (kato...@freaknet.org): > > > Again, links before opinions: > > > > https://sourceforge.net/p/net-tools/code/ci/master/tree/ > > > > net-tools might be obsolete for many functions, but it's still > > developed, and is surely not "unmaintained" since 17 years ago. > > Argue with Jon Corbet, then: > https://lwn.net/Articles/710533/ > > That was last year. I don't believe there's been a substantial > turnaround despite some checkins. (If I'm mistaken, I'lll find out when > I hear people whose judgment I trust say 'A miracle happened and > net-tools has been fully made reasonable to rely on, again.') Yeah, I knew the link, and it correctly says that net-tools has not seen a new release since 2011 (which is 7 years, not 17 :P). And thanks a lot for the link. This is the way a discussion should go :) [cut] > > Jon Corbet was on the glass-half-empty side of the discussion when he > covered procmail's status, but be sure to read the comment thread. > https://lwn.net/Articles/416901/ > [cut] Rick, thanks again for this other link: I will go through the thread, promise, and I am sure I will learn something useful. My whole point was that old does not necessarily mean bad (which seems to have become fancy these days) or gold (which is another dangerous tenet). HND KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
Quoting KatolaZ (kato...@freaknet.org): > Again, links before opinions: > > https://sourceforge.net/p/net-tools/code/ci/master/tree/ > > net-tools might be obsolete for many functions, but it's still > developed, and is surely not "unmaintained" since 17 years ago. Argue with Jon Corbet, then: https://lwn.net/Articles/710533/ That was last year. I don't believe there's been a substantial turnaround despite some checkins. (If I'm mistaken, I'lll find out when I hear people whose judgment I trust say 'A miracle happened and net-tools has been fully made reasonable to rely on, again.') > Let's make another example. procmail Sure, let's discuss procmail. Unlike net-tools, it's a very modestly scoped codebase and not central to system security. Since being orphaned, it's accumulated only two unfixed bugs with alleged security implications that informed observers consider seriously farfetched, not to mention actually being bugs in an Email Sanitizer project and Horde, not procmail itself. So, many including me consider it 'completed' more than it is 'orphaned', and continue to happily use it rather than aspiring replacement such as Maildrop, sieve, and sortmail. Jon Corbet was on the glass-half-empty side of the discussion when he covered procmail's status, but be sure to read the comment thread. https://lwn.net/Articles/416901/ > Is anybody here ready to claim that procmail is useless and we should > replace it just because its development ended 17 years ago, producing > a damn virtually perfect piece of software, that does *one* thing and > does it *well*, has been included in all the Linux and *BSD > distributions in the last 25 years, and did not require any > maintenance at all for 17 long years? o_O Certainly not me. But that didn't stop you from pretending as if I'd advanced that argument. Which was a waste of time on your part, but I hope you enjoyed the typing practice. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
Rowland Penny wrote: > The problem is that it is probably easier to start anew rather than > trying to update/maintain an existing project. You have to contact > the existing maintainer (and you could have problems actually > finding the maintainer), get their permission to update the package > or fix bugs and then do what you wanted to do in the first place. And especially if it's to address things like changed kernel internals - in this case adding a lot of additional information/features. Often it can be the case that the old code isn't easily adapted in anything other than a "write whole new chunks from scratch" approach. By the time you've : made wholesale changes to the internal data structures (eg introducing flexibly sized arrays of values instead of fixed discrete values), made wholesale changes to the data collection routines (eg walking a tree of possible data values rather than reading a few hardcoded ones), and made wholesale changes to the UI (eg parsing new required options, outputting new (and variable) data values) - then it can often be a lot easier, cleaner, and less error prone to start again with a fresh sheet. How many times have we looked at something and though "if only we hadn't started from there". I've got that in the (new to us) house. The plumbing has quite a few "what were they thinking" 'features' - but stepping back, many of them make sense in that (for example) the bathroom plumbing was altered while there was still a hot water cylinder (& cupboard), later that cylinder was removed and a combi boiler fitted, it would have been disruptive to the (relatively newly tiled) bathroom to try and redo those parts of the previous work that no longer made sense. I'll be doing some more alterations myself, but this time I'll be in a position to rip a lot of it out and effectively start again - throwing out some of the historical baggage (I bet some of the plumbing is still pre-metric - ie 1/2" and 3/4" rather than 15mm and 22mm pipe). In other cases, it simply makes sense to gather a collection of "random stuff" into on integrated tool - I'm thinking about the "ip" command here. I bet there was a lot of duplicated stuff in the predecessors (eg route, ifconfig, et al) - with each util having similar code to (eg) interrogate the state of bits of the (IP) networking stack. In addition, it means having one tool (albeit a bigger one) to call on for a group of related functions - eg IP addressing and routing tables are closely and inextricably linked, why have two unrelated tools to manage them ? >> Get their permission? Aren't we using free software? > > If you want to update a packages code, you need to get at it, otherwise > it is called a fork, therefore you need the maintainers permission to > change it. If you don't get permission, then you need a new name - for the package and the binaries installed on the system - to avoid confusion. So then you have the same issue that people will complain "why did they have to change it ?". ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
On Tue, 10 Jul 2018 15:36:46 +0200 Harald Arnesen wrote: > Rowland Penny [2018-07-10 14:37]: > > > The problem is that it is probably easier to start anew rather than > > trying to update/maintain an existing project. You have to contact > > the existing maintainer (and you could have problems actually > > finding the maintainer), get their permission to update the package > > or fix bugs and then do what you wanted to do in the first place. > > Get their permission? Aren't we using free software? If you want to update a packages code, you need to get at it, otherwise it is called a fork, therefore you need the maintainers permission to change it. Rowland ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
Rowland Penny [2018-07-10 14:37]: > The problem is that it is probably easier to start anew rather than > trying to update/maintain an existing project. You have to contact the > existing maintainer (and you could have problems actually finding the > maintainer), get their permission to update the package or fix bugs > and then do what you wanted to do in the first place. Get their permission? Aren't we using free software? -- Hilsen Harald ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
On Tue, 10 Jul 2018 14:08:48 +0200 Harald Arnesen wrote: > Rick Moen [2018-07-10 10:30]: > > > Was there something that lead you to believe it had become illegal > > to use unmaintained code? Otherwise, I find the basis of your > > question quite difficult to understand. > > Don't be ridiculous. I just think it would be better to maintain the > old commands instead of writing something new and different. > > Yes, I know I am free to maintain them myself. The problem is that it is probably easier to start anew rather than trying to update/maintain an existing project. You have to contact the existing maintainer (and you could have problems actually finding the maintainer), get their permission to update the package or fix bugs and then do what you wanted to do in the first place. Whilst I agree it would be nice to maintain the old packages, sometimes it just isn't possible. Rowland ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
Rick Moen [2018-07-10 10:30]: > Was there something that lead you to believe it had become illegal to > use unmaintained code? Otherwise, I find the basis of your question > quite difficult to understand. Don't be ridiculous. I just think it would be better to maintain the old commands instead of writing something new and different. Yes, I know I am free to maintain them myself. -- Hilsen Harald ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
Il giorno Tue, 10 Jul 2018 09:32:07 +0300 Lars Noodén ha scritto: > On 07/09/2018 11:23 PM, Harald Arnesen wrote: >> Rick Moen [2018-07-09 21:01]: >> >>> 'netstat' in the 21st Century is spelled 'ss'. ;-> >>> https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ >>> >> >> Why, oh why replace well-known, portable commands with Linux-only >> commands that are no better? > > Looking at the comparison table in that link, not only are the new > utilities and order of magnitude more complex they also fail to deliver > many of the functions available in the normal utilities. Actually there are many things that make net-tools obsolete to modern networking standards. They do not take advantage of features that were introduced in the kernel in the last dozen years: https://loicpefferkorn.net/2016/03/linux-network-metrics-why-you-should-use-nstat-instead-of-netstat/ However, only nstat retrieves all the metrics provided by the kernel. Netstat seems to skip some of them, breakdown of metrics number per section: [...] Why? Just because netstat maintains a static table of metrics entries, while nstat parses the whole /proc files. Since netstat is obsolete, new entries are not taken into account. [...] However ss is way more comprehensive when it comes to TCP connection internals, by reading /proc/net/tcp. For instance, for an established TCP connection you can retrieve almost every number that characterize the state of an established TCP connection: [...] Another super feature of ss is its filters based on the states of a connection, more handy than grepping netstat output: Then, ifconfig is plain useless when it comes to dealing with multiple IP address assigments to the same interface. Another limitation of ifconfig is it's counters size, that wrap after every 4GiB of data*; the kernel's counters have been larger than that for many years. And it's dropped packets counter meaning is hardly any useful, as it was not updated to reflect the change in what the kernel counts as a dropped packet#. *) https://serverfault.com/questions/163404/ifconfig-showing-wrong-rx-tx-byte-count #) https://www.linuxquestions.org/questions/linux-networking-3/ifconfig-reports-packet-drop-4175507861-print/ Beginning with kernel 2.6.37, it has been changed the meaning of dropped packet count. Before, dropped packets was most likely due to an error. Now, the rx_dropped counter shows statistics for dropped frames because of: Softnet backlog full Bad / Unintended VLAN tags Unknown / Unregistered protocols IPv6 frames when the server is not configured for IPv6 If any frames meet those conditions, they are dropped before the protocol stack and the rx_dropped counter is incremented. > Newer is not better. Different is not better. Only better is better. In the case of net-tools and iptools, newer is indeed much better. Alessandro ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
On Tue, Jul 10, 2018 at 01:30:41AM -0700, Rick Moen wrote: > Quoting Harald Arnesen (skog...@gmail.com): > > > So if my main machine runs *BSD, I will have to use a totally different > > set of commands on my Linux laptop? > > No, you can continue to use a set of utilities on your Linux laptop that > have been unmaintained code for 17 years and cannot handle source-based > routing, QoS, VLAN, bonding, bridges, showing all IP addresses assigned > to an interface, removing an IPv4 address from an interface, etc. > Nothing stopping you. Again, links before opinions: https://sourceforge.net/p/net-tools/code/ci/master/tree/ net-tools might be obsolete for many functions, but it's still developed, and is surely not "unmaintained" since 17 years ago. I am not saying the alternatives are not good or than we shouldn't use them. I am just replying with facts to something that was not factually correct ;) > > Was there something that lead you to believe it had become illegal to > use unmaintained code? Otherwise, I find the basis of your question > quite difficult to understand. > Let's make another example. procmail seems to be one of those pieces of software which is currently unmaintained (even if this statemen is somehow dubious, atm). The last stable release is 3.22 from September 2001 (yes, 2001, almost 17 years ago). There have been no bug reports for more than 17 years, and surely not because procmail is not used any more. Is anybody here ready to claim that procmail is useless and we should replace it just because its development ended 17 years ago, producing a damn virtually perfect piece of software, that does *one* thing and does it *well*, has been included in all the Linux and *BSD distributions in the last 25 years, and did not require any maintenance at all for 17 long years? o_O Oh, come on ;) The staggering majority of us will never have the privilege of developing anything remotely close to that. If the history of only 10% of the software around today was only comparable to that of procmail, we would live in a much much better world, software-wise speaking... HND KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
Quoting Harald Arnesen (skog...@gmail.com): > So if my main machine runs *BSD, I will have to use a totally different > set of commands on my Linux laptop? No, you can continue to use a set of utilities on your Linux laptop that have been unmaintained code for 17 years and cannot handle source-based routing, QoS, VLAN, bonding, bridges, showing all IP addresses assigned to an interface, removing an IPv4 address from an interface, etc. Nothing stopping you. Was there something that lead you to believe it had become illegal to use unmaintained code? Otherwise, I find the basis of your question quite difficult to understand. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
On 10.07.18 09:32, Lars Noodén wrote: > > Why, oh why replace well-known, portable commands with Linux-only > > commands that are no better? > > Looking at the comparison table in that link, not only are the new > utilities and order of magnitude more complex they also fail to deliver > many of the functions available in the normal utilities. Scrolling through the document, I found it an information-free artifact, devoid of any reason to favour the new over the standard. > Newer is not better. Different is not better. Only better is better. > ... and most of these new utilities don't cut the mustard from what I've > experienced with them. Ego drives young men to reinvent the wheel, then declaim "mine is grand, and I deprecate (piss on) the old." (E.g. the only pretext for reimplementing the simulator for AVR microcontrollers was that the new bloke needed a vehicle to massage his C++ ego, so the eminently serviceable C version had to go.) It is not possible to guide them to direct their energies to maintaining the community's existing tools, because it is all about the new egos, not supporting standard tools. No problem. I continue to use ifconfig and netstat, though I have admittedly moved from nslookup to dig. > I haven't decided about ss yet however. Tried it yesterday, after learning that it exists, but am underwhelmed, and cannot see any need to change. Erik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
Rick Moen [2018-07-10 00:31]: > Quoting Harald Arnesen (skog...@gmail.com): > >> Why, oh why replace well-known, portable commands with Linux-only >> commands that are no better? > > At your convenience look up how many years the net-tools codebase has > been orphaned. Can't remember, but it's many.[1] There is also > functionality supported in the iproute2 tools but not in the net-tools > old-standard ones. So if my main machine runs *BSD, I will have to use a totally different set of commands on my Linux laptop? -- Hilsen Harald ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
On 07/09/2018 11:23 PM, Harald Arnesen wrote: > Rick Moen [2018-07-09 21:01]: > >> 'netstat' in the 21st Century is spelled 'ss'. ;-> >> https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ > > Why, oh why replace well-known, portable commands with Linux-only > commands that are no better? Looking at the comparison table in that link, not only are the new utilities and order of magnitude more complex they also fail to deliver many of the functions available in the normal utilities. Newer is not better. Different is not better. Only better is better. ... and most of these new utilities don't cut the mustard from what I've experienced with them. I haven't decided about ss yet however. /Lars ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
On Mon, Jul 09, 2018 at 12:01:06PM -0700, Rick Moen wrote: > Quoting k...@aspodata.se (k...@aspodata.se): > > > Nice, didn't know about the ss command. You can also use > > netstat -tulp > > lsof -i :80 > > 'netstat' in the 21st Century is spelled 'ss'. ;-> > https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ And in this case, there _is_ a relevant difference: netstat -p lists only one process per socket despite them often being shared. ss -p handles them correctly. Meow. -- // If you believe in so-called "intellectual property", please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable And Non-Discriminatory prices. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
Il giorno Mon, 9 Jul 2018 22:23:04 +0200 Harald Arnesen ha scritto: > Rick Moen [2018-07-09 21:01]: > > > 'netstat' in the 21st Century is spelled 'ss'. ;-> > > https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ > > > > Why, oh why replace well-known, portable commands with Linux-only > commands that are no better? Because: "These programs (except iwconfig) are included in the net-tools package that has been unmaintained for years. The functionality provided by several of these utilities has been reproduced and improved in the new iproute2 suite, primarily by using its new ip command." So, in short: because they *are* better! Alessandro ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
Quoting Harald Arnesen (skog...@gmail.com): > Why, oh why replace well-known, portable commands with Linux-only > commands that are no better? At your convenience look up how many years the net-tools codebase has been orphaned. Can't remember, but it's many.[1] There is also functionality supported in the iproute2 tools but not in the net-tools old-standard ones. Isn't this a revival of a discussion that's been done to death? [1] Looked it up for you: 2001. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
Harald Arnesen wrote on 07/09/2018 03:23 PM: > Why, oh why replace well-known, portable commands with Linux-only > commands that are no better? Can we blame SCO or Microsoft somehow? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
Rick Moen [2018-07-09 21:01]: > 'netstat' in the 21st Century is spelled 'ss'. ;-> > https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ Why, oh why replace well-known, portable commands with Linux-only commands that are no better? -- Hilsen Harald ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
Quoting k...@aspodata.se (k...@aspodata.se): > Nice, didn't know about the ss command. You can also use > netstat -tulp > lsof -i :80 'netstat' in the 21st Century is spelled 'ss'. ;-> https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ (My brain still defaults to the various net-tools utilities, too, But at least I cured it of the urge to use 'nslookup' a decade or so ago.) -- Cheers, "I am a member of a civilization (IAAMOAC). Step back Rick Moenfrom anger. Study how awful our ancestors had it, yet r...@linuxmafia.com they struggled to get you here. Repay them by appreciating McQ! (4x80) the civilization you inherited." -- David Brin ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
Adam Borowski: > On Sun, Jul 08, 2018 at 09:12:12PM -0400, Hendrik Boom wrote: > > I can't start lighttpd because something is already bound to port 80. > > > > How can I find out what's attached to this port? > > man ss > > ss -lp46 Nice, didn't know about the ss command. You can also use netstat -tulp lsof -i :80 Regards, /Karl Hammar --- Aspö Data Lilla Aspö 148 S-742 94 Östhammar Sweden +46 173 140 57 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
On Sun, Jul 08, 2018 at 09:12:12PM -0400, Hendrik Boom wrote: > I can't start lighttpd because something is already bound to port 80. > > How can I find out what's attached to this port? > $ netstat -lntpu $ man netstat HND KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
On 07/08/2018 06:12 PM, Hendrik Boom wrote: I can't start lighttpd because something is already bound to port 80. How can I find out what's attached to this port? -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng I'd run this command: sudo lsof -nP | grep TCP | grep :80 You may need to install lsof first ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] who's tying up my port 80?
On Sun, Jul 08, 2018 at 09:12:12PM -0400, Hendrik Boom wrote: > I can't start lighttpd because something is already bound to port 80. > > How can I find out what's attached to this port? man ss ss -lp46 -- // If you believe in so-called "intellectual property", please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable And Non-Discriminatory prices. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] who's tying up my port 80?
I can't start lighttpd because something is already bound to port 80. How can I find out what's attached to this port? -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
