Thanks for everybody's answers... :)
R.
2008/6/20 Pietro Gagliardi <[EMAIL PROTECTED]>:
> On Jun 20, 2008, at 10:03 AM, Rudolf Sykora wrote:
>
> Hello,
>>
>> is there any simple way how to identify processes belonging to one
>> concrete process group?
>>
>
> They're called "note groups" and the
> ahci0 port 0xf0704000: hba sss 0; ncs 31; coal 1; mport 2; led 1; clo 1; ems
> 0;
> ich: sata-II with 3 ports
>
> and this is the lspci -vvv output:
>
> 00:1f.2 SATA controller: Intel Corporation Mobile SATA AHCI Controller
> (rev 03) (prog-if 01 [AHCI 1.0])
[...]
looking through the sources
shouldn't the sig be
extern voidsetmalloctag(void*, void*);
or
extern voidsetmalloctag(void*, uintptr);
(matching ndbsetrealloctag and convention) not
extern voidsetmalloctag(void*, ulong);
since on a mythical 64-bit machine, ulong is 32bits but
addresses ar
Hi,
When I open a window in rio, run 9fat:, and then exit, the window gets
'stuck'. That is, it just sits there, I can't type anything in it
anymore.
Apparently, it is waiting for dossrv to exit (which gets started by
9fat:): when I open a second window, and run 'kill dossrv | rc', the
first windo
> This (being unable to exit the window without killing dossrv) seems a
> bit strange to me. I can of course destroy the window using the
> 'Delete' option in rio's menu, but I think that's not the 'right' way
> to do it.
> Am I doing something wrong (is there a way I can actually exit said
> windo
On Jun 21, 2008, at 2:21 PM, Sander van Dijk wrote:
This (being unable to exit the window without killing dossrv) seems a
bit strange to me. I can of course destroy the window using the
'Delete' option in rio's menu, but I think that's not the 'right' way
to do it.
Am I doing something wrong (is
> It's happened to me quite often. I think rc should kill all
> subprocesses on exit
No. It shouldn't, and it doesn't.
> How I wish Plan 9 had kill -9! The kernel uses the note
>
> sys: killed
>
> internally, but notify(2) doesn't say so. I wonder...
Plan 9 is not Unix.
echo
> When I open a window in rio, run 9fat:, and then exit, the window gets
> 'stuck'. That is, it just sits there, I can't type anything in it
> anymore.
> Apparently, it is waiting for dossrv to exit (which gets started by
> 9fat:): when I open a second window, and run 'kill dossrv | rc', the
> firs
You didn't tell us much about your memory usage patterns.
Do you allocate large lots of large objects and then
free them? That would explain the larger footprint
and the identical umem. Do you agree with the second
allocation profile?
It is easily possible that aux/acidleak's bitmap code
is not
