Re: ls problem on solaris 5.8
From: Barry Margolin (barmar_at_alum.mit.edu)
Date: 01/29/04
- Next message: Sameer: "very odd problem with hme1"
- Previous message: Luca Ferrari: "Re: ls problem on solaris 5.8"
- In reply to: Luca Ferrari: "Re: ls problem on solaris 5.8"
- Next in thread: Michael Tosch: "Re: ls problem on solaris 5.8"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 29 Jan 2004 08:56:02 GMT
In article
<604905b75b661268523b275f34a8a42c.60620@mygate.mailgate.org>,
"Luca Ferrari" <fluca1978@libero.it> wrote:
> pipe() = 4 [5]
> fork() = 4821
> close(5) = 0
> close(2) = 0
> fstat64(4, 0xFFBEF908) = 0
> brk(0x00076988) = 0
> brk(0x00078988) = 0
> ioctl(4, TCGETA, 0xFFBEF894) Err#22 EINVAL
> read(4, 0x0007624C, 5120) = 0
> llseek(4, 0, SEEK_CUR) Err#29 ESPIPE
> close(4) = 0
I think you've got a bogus "ls" command. I can't think of a reason why
it would need to fork a child process and talk to it with a pipe.
Maybe you've been rootkitted.
-- Barry Margolin, barmar@alum.mit.edu Arlington, MA *** PLEASE post questions in newsgroups, not directly to me ***
- Next message: Sameer: "very odd problem with hme1"
- Previous message: Luca Ferrari: "Re: ls problem on solaris 5.8"
- In reply to: Luca Ferrari: "Re: ls problem on solaris 5.8"
- Next in thread: Michael Tosch: "Re: ls problem on solaris 5.8"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|