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

  • Home
  • SEARCH
  • 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 3843714
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 19, 20262026-05-19T15:58:38+00:00 2026-05-19T15:58:38+00:00

I have a problem analogous to the one described here: Prevent fork() from copying

  • 0

I have a problem analogous to the one described here:
Prevent fork() from copying sockets

Basically, inside my Lua script I’m spawning another script which:

  • doesn’t require communicating with my script either way
  • continues running after my script had finished
  • is a 3rd party program, code of which I have no control over

The problem is that my Lua script opens a TCP socket to listen on a specific port and after it’s quit and despite an explicit server:close() the child (or more specifically its children) holds onto the socket and keeps the port open (in LISTEN state) preventing my script from running again.

Here’s example code that demonstrates the problem:

require('socket')

print('listening')
s = socket.bind("*", 9999)
s:settimeout(1)

while true do
    print('accepting connection')
    local c = s:accept()
    if c then
            c:settimeout(1)
            local rec = c:receive()
            print('received ' .. rec)
            c:close()
            if rec == "quit" then break end
            if rec == "exec" then 
                    print('running ping in background')
                    os.execute('sleep 10s &')
                    break
            end     
    end
end
print('closing server')
s:close()

If I run the above script and echo quit | nc localhost 9999 everything works well – program quits and port is closed.

However if I do echo exec | nc localhost 9999 the program quits but the port is blocked by the spawned sleep (as confirmed by netstat -lpn) until it exits.

How do I tackle this in the simplest possible manner, preferably without adding any extra dependencies.

  • 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-19T15:58:39+00:00Added an answer on May 19, 2026 at 3:58 pm

    I found a much simpler solution which utilizes the fact that os.execute(cmd) runs cmd in a shell, which, as it turns out, is capable of closing file descriptors as seen here:

    • http://linux.die.net/man/1/ash (section Redirections )

    • http://www.gnu.org/software/bash/manual/bashref.html#Redirections


    For example (tested in ash):

        exec 3<&-                                      # closes fd3
        exec 3<&- 4<&-                                 # closes fd3 and fd4
        eval exec `seq 1 255 | sed -e 's/.*/&<\&-/'`   # closes all file descriptors 
    

    So in my luasocket based example it’s enough to replace:

        os.execute('sleep 10s &')
    

    with:

        os.execute("eval exec `seq 1 255 | sed -e 's/.*/&<\\&-/'`; sleep 10s &")
    

    This closes all file descriptors, including my server socket, before executing the actual command (here sleep 10s) so that it doesn’t hog the port after my script exits. It also has the bonus of taking care of stdout and stderr redirection.

    This is much more compact and uncomplicated than working around Lua‘s limitations and doesn’t require any extra dependencies. Thanks go to #uclibc where I got some brilliant help with final shell syntax from the embedded linux crew.

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

Sidebar

Related Questions

I have problem in some JavaScript that I am writing where the Switch statement
I have problem with return statment >.< I want to store all magazine names
I have problem with starting processes in impersonated context in ASP.NET 2.0. I am
I have problem compilin this code..can anyone tell whats wrong with the syntax CREATE
I have problem with ActionLink. I'd like to pass to my ActionLink parameter for
I have problem when I try insert some data to Informix TEXT column via
I do not have problem as such but I am quite new to Ruby.
I have a problem using the Java search function in Eclipse on a particular
I have a problem with a little .Net web application which uses the Amazon
I have a problem in my project with the .designer which as everyone know

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.