Date: Mon, 30 Apr 2001 11:18:41 +0300 From: Valentin Nechayev <netch@iv.nn.kiev.ua> To: Mike Meyer <mwm@mired.org> Cc: stable@FreeBSD.ORG Subject: Re: tail Message-ID: <20010430111841.B646@iv.nn.kiev.ua> In-Reply-To: <15085.3399.399194.624320@guru.mired.org>; from mwm@mired.org on Mon, Apr 30, 2001 at 01:59:19AM -0500 References: <15085.1672.680397.456359@guru.mired.org> <KPECIILENDDLPCNIMLOFIEOLCCAA.juha@saarinen.org> <15085.3399.399194.624320@guru.mired.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Mon, Apr 30, 2001 at 01:59:19, mwm (Mike Meyer) wrote about "RE: tail": > Yes, there is. If you're monitoring a programm that creates a lot of > files in a previously empty directory (for example, extracting a tar > file into it), then: > > tail -f targetdir > > will do the trick, though it would be better to clean up the output > (cat -v, maybe). And its output is related to flat format of directory in specific file system. You will provide decrypting module for each file system for each platform, won't you? `man kevent' saves you. > Deciding for the users what actions are an error and which aren't is a > *really* nasty habit. Let's allow them 'rm -rf /' > Windows does it all to often, which is one of > the reasons Windows sucks. Linux - at least some distributions - seems > to have picked up the habit from Windows. Oh well. Windows have no problems such as '/tmp race conditions'. /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010430111841.B646>