From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <c3c0894654e5b89c4a1346075c3167cf@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] broken vac
From: rog@vitanuova.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Mon,  3 Feb 2003 14:53:03 +0000
Topicbox-Message-UUID: 4d4b4558-eacb-11e9-9e20-41e7f4b1d025

axel:
> I tried: cmp /proc/number/text /bin/vac
> which did not report differences; is that what I need,
> or will the text file point to the new binary if I update
> the binary on the system?

russ:
> The cmp is fine.   You have the latest vac.
> Something else is wrong.

actually, i'm not sure that's right.  the text file just points to the
file on the filesystem, so unless that's been removed/renamed in the
meantime (safeinstall?)  the cmp is unlikely to tell you much.
looking in the dump might be more informative.

  cheers,
    rog.

% cat tst.c
#include <u.h>
#include <libc.h>
void
main(void)
{
	sleep(2000000);
}
% 8c tst.c && 8l tst.8
% 8.out &
% echo $apid
600
% md5sum /proc/600/text
416079107feb6f50ad2204838f6a49c2	/proc/600/text
% ed tst.c
,s/2000/1000/p
	sleep(1000000);
w
70
q
% % 8c tst.c && 8l tst.8
% md5sum /proc/600/text
15d26908dcf5ee6a2919a255cd1f2a02	/proc/600/text
% md5sum 8.out
15d26908dcf5ee6a2919a255cd1f2a02	8.out
%