Messages in this thread | | | Subject | Re: Reserving "special" port numbers in the kernel ? | From | Sean Neakums <> | Date | Sat, 16 Nov 2002 00:58:17 +0000 |
| |
commence Arun Sharma quotation:
> xavier.bestel@free.fr (Xavier Bestel) writes: > >> Le sam 16/11/2002 à 01:00, Arun Sharma a écrit : >> > One of the Intel server platforms has a magic port number (623) that >> > it uses for remote server management. However, neither the kernel nor >> > glibc are aware of this special port. >> > >> > As a result, when someone requests a privileged port using >> > bindresvport(3), they may get this port back and bad things happen. >> > >> > Has anyone run into this or similar problems before ? Thoughts on >> > what's the right place to handle this issue ? >> >> run a dummy app at startup which reserves that port ? > > Yes, I'm already aware of this one, but was looking for a lighter weight > solution (ideally a config file change) that doesn't involve running an > extra process (think of doing this on a large number of machines).
inetd
-- / | [|] Sean Neakums | Questions are a burden to others; [|] <sneakums@zork.net> | answers a prison for oneself. \ | - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |