* Oliver Fromme <[EMAIL PROTECTED]> [2006-02-09 15:32]:
> Jens Trzaska <[EMAIL PROTECTED]> wrote:
> > David Kirchner <[EMAIL PROTECTED]> [2006-02-08 16:53]:
> > > The memory is apparently locked in core, according to the L flag for
> > > 'ps'. This should probably be documented in the truss man
Jens Trzaska <[EMAIL PROTECTED]> wrote:
> David Kirchner <[EMAIL PROTECTED]> [2006-02-08 16:53]:
> > 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
On Thu, Feb 09, 2006 at 01:25:30PM +0100, Jens Trzaska wrote:
> 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?
The 'L' flag in ps output corresponds to either the
* David Kirchner <[EMAIL PROTECTED]> [2006-02-08 16:53]:
> On 2/8/06, Jens Trzaska <[EMAIL PROTECTED]> wrote:
> >
> > I just tried to use truss on the running /sbin/init process.
> >
> > [EMAIL PROTECTED]:~# truss -p 1
> > truss: cannot open /proc/1/mem: No such file or directory
>
On 2/8/06, Jens Trzaska <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I just tried to use truss on the running /sbin/init process.
>
> [EMAIL PROTECTED]:~# 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
Hi,
I just tried to use truss on the running /sbin/init process.
[EMAIL PROTECTED]:~# 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 mo
