From owner-freebsd-current Mon Oct 19 03:06:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA15709 for freebsd-current-outgoing; Mon, 19 Oct 1998 03:06:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.ftf.dk (mail.ftf.net [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA15704 for ; Mon, 19 Oct 1998 03:06:54 -0700 (PDT) (envelope-from regnauld@deepo.prosa.dk) Received: from mail.prosa.dk ([192.168.100.254]) by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id MAA04681 for ; Mon, 19 Oct 1998 12:11:32 +0200 (CEST) (envelope-from regnauld@deepo.prosa.dk) X-Authentication-Warning: mail.ftf.dk: Host [192.168.100.254] claimed to be mail.prosa.dk Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id MAA00180 for ; Mon, 19 Oct 1998 12:27:08 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id MAA22724; Mon, 19 Oct 1998 12:06:30 +0200 (CEST) Message-ID: <19981019120630.61686@deepo.prosa.dk> Date: Mon, 19 Oct 1998 12:06:30 +0200 From: Philippe Regnauld To: current@FreeBSD.ORG Subject: truss && init Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e X-Operating-System: FreeBSD 2.2.6-RELEASE i386 Phone: +45 3336 4148 Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 1) On 3.0-R (and -current from a week ago), the ktrace(1) man page mentions: -p pid Enable (disable) tracing on the indicated process id (only one -p flag is permitted). For fun, I decided to try: ktrace -p 1 ... and it works: every time I kill some random getty, the getty is respawned and the relevant stuff is logged in ./ktrace.out. However, subsequent invokations of "ktrace -p 1" do NOT turn off the tracing (it only resets the ktrace.out file, and logging continues). Only way out -> reboot or symlink to /dev/null (haven't tried) otherwise you risk filling the disk. 2) Still on 3.0-R, truss(1) mentions: # Follow an already-running process $ truss -p 1 ... and that works, though on a recent -current (~1 week ago), it hung my machine. Will try to reproduce. -- -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]- The Internet is busy. Please try again later. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message