Date: Thu, 9 Feb 2006 13:25:30 +0100 From: Jens Trzaska <jt@barfoos.de> To: David Kirchner <dpk@dpk.net> Cc: freebsd-stable@freebsd.org Subject: Re: truss and /sbin/init Message-ID: <20060209122530.GA36749@anastasia.lan.barfoos.de> In-Reply-To: <35c231bf0602080751p6df719f0sf61cee25d3404a8@mail.gmail.com> References: <20060208152546.GA78035@anastasia.lan.barfoos.de> <35c231bf0602080751p6df719f0sf61cee25d3404a8@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* David Kirchner <dpk@dpk.net> [2006-02-08 16:53]: > On 2/8/06, Jens Trzaska <jt@barfoos.de> wrote: > > > > I just tried to use truss on the running /sbin/init process. > > > > root@beast:~# truss -p 1 > > truss: cannot open /proc/1/mem: No such file or directory > > Exit 8 > > > > As you can see without any luck. But why is the memory information > > missing in procfs here? /sbin/init is a more or less regular userland > > process. Looking at truss(1) it even shows this example: > > The memory is apparently locked in core, according to the L flag for > 'ps'. This should probably be documented in the truss man page to > avoid confusion. Does you or perhaps someone else know why init is locked in core? Its not the case in 4.x and I can't see why a regular userspace process is locked. Can someone explain that? jens
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060209122530.GA36749>