From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17860 invoked by alias); 2 Sep 2005 17:14:05 -0000 Mailing-List: contact systemtap-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sources.redhat.com Received: (qmail 17837 invoked by uid 22791); 2 Sep 2005 17:13:57 -0000 Subject: Re: how to remove shellsnoop? From: Martin Hunt To: CHANG Xiaolin Cc: systemtap@sources.redhat.com In-Reply-To: <1971.219.239.136.141.1125640504.squirrel@sqmail.ust.hk> References: <1125547048.11102.21.camel@dragon> <20050901150038.GB9569@redhat.com> <1971.219.239.136.141.1125640504.squirrel@sqmail.ust.hk> Content-Type: text/plain Organization: Red Hat Inc. Date: Fri, 02 Sep 2005 17:14:00 -0000 Message-Id: <1125681234.3489.3.camel@dragon> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) Content-Transfer-Encoding: 7bit X-SW-Source: 2005-q3/txt/msg00430.txt.bz2 On Fri, 2005-09-02 at 13:55 +0800, CHANG Xiaolin wrote: > Hi, > I "insmod runtime/probes/shellsnoop/shellsnoop.ko". That is a bad idea, but it should be harmless. > There is no error. > But when I "rmmod shellsnoop", the computer restarts. > > Could anyone explain the reason? We can not use rmmod to remove > shellsnoop modules? if not, how to remove shellsnoop module ? I tried this on several different OSes and cpus and it never happened to me, so I cannot guess what is going on. The only supported way to load modules built using the systemtap runtime is with stpd. From the systemtap directory, it would be "../../stpd/stpd shellsnoop.ko" Or install stpd in your path and you can just do "stpd shellsnoop.ko" Martin