Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 17 Nov 2002 11:30:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 17 Nov 2002 11:30:28 -0500 Received: from fmr03.intel.com ([143.183.121.5]:14330 "EHLO hermes.sc.intel.com") by vger.kernel.org with ESMTP id ; Sun, 17 Nov 2002 11:30:27 -0500 To: Alan Cox Cc: Linux Kernel Mailing List Subject: Re: Reserving "special" port numbers in the kernel ? References: <1037414638.21937.20.camel@irongate.swansea.linux.org.uk> From: Arun Sharma Date: 17 Nov 2002 08:37:19 -0800 In-Reply-To: <1037414638.21937.20.camel@irongate.swansea.linux.org.uk> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1146 Lines: 27 Alan Cox writes: > On Sat, 2002-11-16 at 00:00, Arun Sharma wrote: > > 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. > > I can't find it in the IETF standards documents either. It's been registered as a well known port: http://www.iana.org/assignments/port-numbers [..] > > > Has anyone run into this or similar problems before ? Thoughts on > > what's the right place to handle this issue ? > > Run your remote management daemon from xinetd, it'll then get the port > nice and early in the system runtime. The thing that's unique about our situation is that the daemon in not user level. It runs at hardware/firmware level, so that you can remotely administer the machine even when software is malfunctioning. -Arun - 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/