Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6130703
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T16:53:22+00:00 2026-05-23T16:53:22+00:00

When I do lsof -nl | egrep TCP|UDP in order to see socket states,

  • 0

When I do “lsof -nl | egrep “TCP|UDP” ” in order to see socket states, I notice that the sockets that I expected to be listed are not at all, but when I do a “netstat –tcp”, they are listed, but are in a CLOSE_WAIT state.

What I know so far is that the CLOSE_WAIT state signifies that my application has a responsibility now to explicitly close this socket (but there is a bug that I’m trying to track down, which keeps this socket in a CLOSE_WAIT state). I thought that if a socket exists, then it must have an open file descriptor associated with it, so I expected to see it on the output of lsof. Why is it that I couldn’t see it there?

Thanks,
Sandra

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-23T16:53:22+00:00Added an answer on May 23, 2026 at 4:53 pm

    Do you have enough permissions? (And I think this belongs to superuser)

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a client tcp socket (in c++) that has a loop where it
You can use command lsof to get file descriptors for all running processes, but
Both netstat -p and lsof -n -i -P seems to readlinking all processes fd's,
One of my favourite tools for linux is lsof - a real swiss army
I'm trying to test a single file if it is open using lsof. Is
What is can't identify protocol when I run the command /usr/sbin/lsof -p 20085 .
I have a file that was deleted, but is still held open my a
Given that with the way Firefox now works, it's somewhat infeasible to specify the
I was wondering, if the output of lsof -i sshd 21880 root 3r IPv4
From time to time, a file that I'm interested in is modified by some

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.