Dan Nelson <[EMAIL PROTECTED]> wrote:
> In the last episode (Jan 23), Oliver Fromme said:
> > Dan Nelson <[EMAIL PROTECTED]> wrote:
> > > In the last episode (Jan 23), Oliver Fromme said:
> > > > I've got a problem on a 4.7-RELEASE machine. I tried using
> > > > /usr/bin/truss on a process
In the last episode (Jan 23), Oliver Fromme said:
> Dan Nelson <[EMAIL PROTECTED]> wrote:
> > In the last episode (Jan 23), Oliver Fromme said:
> > > I've got a problem on a 4.7-RELEASE machine. I tried using
> > > /usr/bin/truss on a process (which was running in a chroot
> > > environment, w
Dan Nelson <[EMAIL PROTECTED]> wrote:
> In the last episode (Jan 23), Oliver Fromme said:
> > I've got a problem on a 4.7-RELEASE machine. I tried using
> > /usr/bin/truss on a process (which was running in a chroot
> > environment, which in turn is on an NFS-mounted filesystem,
> > if that m
In the last episode (Jan 23), Oliver Fromme said:
> Hi,
>
> I've got a problem on a 4.7-RELEASE machine. I tried using
> /usr/bin/truss on a process (which was running in a chroot
> environment, which in turn is on an NFS-mounted filesystem,
> if that matters). But now I cannot kill the truss pr
Fernando Gleiser <[EMAIL PROTECTED]> wrote:
> > Accoding to ps, the truss process is in "disk wait" ("D"),
> > but all disks are working perfectly fine, including the
> > NFS-mounted filesystems.
> >
> > The process that had been trussed ("jws") doesn't run any-
> > more (I had to kill it, us
> Accoding to ps, the truss process is in "disk wait" ("D"),
> but all disks are working perfectly fine, including the
> NFS-mounted filesystems.
>
> The process that had been trussed ("jws") doesn't run any-
> more (I had to kill it, using SIGKILL, I think).
Welcome to NFS hell. That's why you sh
