truss and /sbin/init

[Jens Trzaska]

* David Kirchner <dpk at dpk.net> [2006-02-08 16:53]:
> On 2/8/06, Jens Trzaska <jt at barfoos.de> wrote:
> >
> > I just tried to use truss on the running /sbin/init process.
> >
> >         root at 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