The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
all the bytes.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
vailable for inspection later about the writes it sees. But that's
> hard to write.
You could get much of that information by ktracing and looking for the
relevant calls - {,p}write{,v} and lseek seem to me to be the most
likely candidates.
/~\ The ASCII Mouse
\ /
actually think you will have trouble even
_defining_ what "100% right" is for this test, since everything about
sparseness, right down to whether it's even a thing, is
filesystem-dependent.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
you having the resources (disk space,
time, and energy/motivation) to do that.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
(If trying to build a new kernel SEGVs, maybe
cross-build it?)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
chines? I'm wondering
if perhaps something is broken in a subtle way such that it manifests
on only certain hardware (I'm talking about something along the lines
of "this tickles erratum #2188 in stepping 478 of Intel CPUs from the
Forest Lawn family").
/~\ The ASCII
don't mind losing it for
long enough to find everything using TCP "OOB".
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
y broken, but I doubt I'd
actually find any use for the latter. I might rip out the OOB stuff
just to find and fix anything trying to use it, though.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8
AC DM
that makes up part of a synch; ignoring the urgent bit means that
dropping won't happen. (Does that matter in practice? Probably not,
especially given how little TELNET is used outside walled gardens. But
it still is a correctness issue.)
/~\ The ASCII Mouse
\ / Ribbon
roperly_?), and provided your and the peer's
implementations agree on which sequence number goes in the urgent
field.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
revents bitmasks is really not
useful without STREAMS.").
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
That's part of what I was wondering.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
> Also, I suspect mouse was thinking of the TCP URG concept, and not
> PUSH when he wrote what he did, but I don't know for sure.
Ouch. Yes, you are entirely correct in that regard. Total braino on
my part. My apologies.
/~\ The ASCII Mouse
\ / Ribbon Campa
figured it was still workt asking.
>> ... I'd still be curious where it came from.
> Those answers are CVS:
Not where it came from in the sense of who committed it or what it
looked like at the time, but rather where that person got the various
distinctions from.
/~\ The ASCII
be fixed, but, even
if that reading is correct, I'd still be curious where it came from.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
till.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
> Thanks Mouse and Martin. I got past that error. But now I'm running
> into another problem - unable to determine when write op occurs (to
> be able to return ENOSPC error).
> I want to return ENOSPC error whenever write occurs. Which variable
> contains this info? I'm confuse
ally, I'd start by rereading the code, but I assume you've
already done that.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
text (an important caveat!), a time
difference as short as (1602-802)/44.1=18.14+ milliseconds is clearly
discernible to me.
This is, of course, a situation designed to perceive a very small
difference. I'm sure there are plenty of contexts in which I would
fail to notice even 200ms of delay.
/~\ The ASCII
ick tests, but trying
to figure out an issue on a version I don't use except at work is
something I am unmotivated to do on my own time, and using work time to
dig after an issue that doesn't affect work's use case isn't an
appropriate use of work resources.
/~\ The ASCII Mouse
\
.
But then, so is every other ITIMER_REAL I've ever used.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
re
> correct POSIX periodic timers can attain a target _average_ interval
> between expirations [...]
I would argue that it's misleading, to the point I would call it
incorrect, to call such a thing "periodic".
/~\ The ASCII Mouse
\ / Ribbon Campai
th a high-res wallclock), but
not for timer reloads.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
violates POLA hard.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
1.4T is demonstration-by-example that
it is entirely possible to get this right, even in a tickful system.
(I don't know whether 1.4T sleeps may be slightly too short; I haven't
tested that. But, even if so, fixing that should not involve breaking
timer reloads.)
/~\ The ASCII
. After taking 6000 timestamps (which ideally should take
60.00 seconds), it then prints out all the timestamps, thus indicating
the actual rate signals were delivered at. It's on
ftp.rodents-montreal.org (which supports HTTP fetches as well as FTP)
in /mouse/misc/test-alrm.c for anyone interested
many things called "class"
here. "Group"? "Category"? "Collection"?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
be better for this to be a namespace specific to
config(1) and userconf rather than having anything to do with DV_*
values.
Or is that getting into "the best is the enemy of the good" territory?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@r
ge for them, which is a mild negative
to me; the xsrc trees I have on hand don't have any *.rst files.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
ge, but I prefer that to no doc - and, without any
manpage, I have no idea how someone looking for doc would know to look
for .rst (!) files buried in xsrc, for doc on something in the kernel.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rode
I saw quoted,
sounds likely), you could even do it entirely in userland, immediately
upon having a writable persistent filesystem available.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
anic=1 during boot.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
ace of extreme use cases, but that's hardly
impossible.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
nt?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
boundaries, which I thought was more or less where we
started: defines the API to the vnode subsystem,
including types, #defines, externs, etc. But I'm not sure how that
would differ from what we have now.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
de files involved is broken. I've
been making small steps towards fixing this in my own trees, but it's
still a major mess.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
ne with (what I see as) an inaccurate
name than see the division not done.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
t, int)', not so much.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
and you lose
much of the typechecking.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
"struct"
needs a tag to be useful, and at least a few other identifiers to make
a useful statement, but it sure feels like it occasionally).
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
filesystem-specific).
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
ension, use it, it turns out to be
useful, it gets popular
I've done it myself (well, except for the "gets popular" part, which no
one person can do alone): labeled control structure, AF_TIMER sockets,
pidconn, validusershell, the list goes on.
/~\ The ASCII
g about.
> All of this is not _independent_ of fixing uiomove callers, [...],
> but it's largely orthogonal to the original problem of incorrectly
> rolling back partial uiomoves. :-(
Agreed.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@roden
y use case) or some
such.
Finding good names is a mess.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
oskip, it _is_ skip semantics. The bytes skipped are not copied
anywhere, not by uioskip. (They may have been copied earlier with
uiopeek, but that doesn't affect what uioskip does.) If you want
skip-*with*-copy, well, uiomove is still there.
/~\ The ASCII Mouse
\ / Ribbon C
a bug waiting to happen.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
fields in any
version I have, but it is (presumably carefully) defined so there is no
need for them, either. At least assuming a power-of-two
octet-addressed machine, a char * that's no bigger than 8 bytes, and a
non-malicious compiler.)
/~\ The ASCII Mouse
\ / Ribbon Campa
that _someone_ thought it
reasonable to checksum before swapping, so I can't help wondering what
use case that's appropriate for.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D
h
O_REOPEN a distant third.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
ox looks like internally. But the UI design is
bad enough I would expect the internals to be little better.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
n-trivial code).
What about having it default to a per-proces (or per-thread) settable
state?
Mouse
ow?
> (also, "mirabile visu")
What did I write?
*checks*
Oops. Thanks.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
eventually. This also
means divorcing "non-blocking open" from "non-blocking I/O after open".
So: does anyone have any comments on the above analysis, or thoughts on
good, bad, or even just notable effects making it real per-descriptor
state might have?
/~\ The ASCII
peration".
...ish. I hadn't thought of that. But, the way the code is
structured, that actually isn't a crazy suggestion at all.
I'm not sure it would work, but it's a very good thought.
Thank you!
Mouse
pare Time
Mouse
~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
rocess which reads - blockingly - from stdin and writes the data to a
pipe; that pipe is then set nonblocking in the main process and is
independent of everything else. I might need a third process to make
the reader process die reliably
/~\ The ASCII Mouse
\ / Ribbon
ration rather than of the object. Even aside from
installed-base arguments, I'm not sure whether I think non-blocking
mode on the object should go away. I'd have to think about it more.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-mont
cked
doesn't have any such flag - it merely has room for it).
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
the file,
Hm, okay, I can see how the second flock call in my test was taken as
an attempt to equalgrade (neither upgrade nor downgrade) the exclusive
lock to another exclusive lock.
I'll have to think more about my locking paradigm.
/~\ The ASCII Mouse
\ / Ribbon Ca
e
fork, so the parent and child open separately, I do, of course, get the
expected EWOULDBLOCK from one process.
Is this expected behaviour, or is it a bug?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D
ng something and killing the process.
Obviously, that code would not survive into the end result, but
something like it might be a useful intermediate step.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email!
ce tree in /usr/src.
Is this enough of a bug that it's worth sending-pr? Or is this a case
of me expecting something that's no longer supported to work?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email!
../compile/
> make -j 4 >& make.log
I'd prefer to avoid assuming the user who wants to build the kernel can
write into the source directory tree. You may note the source tree was
(admittedly only by implication) owned by abcxyz but I was doing the
build as mouse.
That said, this does appea
cryptic message about absvdi2.c). Note in particular
that the source tree content was identical; only the path and ownership
differed.
Is this a bug? Or am I doing something wrong?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...
significant fraction of the useful meaning.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
the major number, whether chosen
at module load time or chosen at kernel build time, into the /dev/xyz0
special file in the filesystem. That requires exfiltrating it from the
kernel *somehow*
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo..
nd even
that is relatively weak, given how many "vt100" emulations are at least
as far from VT-100s as wscons is).
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
ot; for basically this
reason. (The difference between ansi and decansi is support for
various DEC extensions, such as scrolling regions or ?-flagged
arguments to CSI h and CSI l.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-mont
VT-100s (mostly things
wscons implements but VT-100s don't) and having a handful of other
mismatches (such as supporting sizes other than 80x24 and 132x24).
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email!
ises free technical support. I suppose I should try
to chase down a contact (the packaging gives no hint whom to contact
for that promised support) and ask. At worst I'll be told nothing
useful.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo..
don't like the way the command is timing out. I find
it far more plausible that I'm doing something wrong.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
) zero.
though it seems to me (b)(C) is actually a special case of (b)(B). See
table 33, later on that page, for more.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
he interfaces the -current tool
> uses are available in -9 kernels.
I did bring over the 9.2 syssrc set, so I should be able to figure
_something_ out.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
d with does
analogously. Until I saw your email, I had no idea there was even any
way to _represent_ multiple ranges in a single request.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
ther than `wdccommand' for the
> ATA_DATA_SET_MANAGEMENT command. All this from [FreeBSD]
And presumably the NetBSD wdccommand/wdccommandext difference matches
the FreeBSD one closely enough for that to be relevant? I shall have
to read wdccommand* over in more detail.
Mouse
wd0 access locks up during the TRIM attempt. One read got through
between that and the cache flush; it locked up again during that. It
then came back. But when I tried to read wd1 it locked up again during
that.
Dunno what all this means
/~\ The ASCII Mous
p,);
>> printf("TRIM %s: returned %d\n",device_xname(wd->sc_dev),rv);
>> return(0);
>> }
> Ah, shouldn't `cmd' be allocated memory rather than being a
> locally-scoped variable?
Why? cmd.flags specifies AT_WAIT, and as I re
e except some time.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
like a rather broken
response to such issues, I've seen brokener.)
Mouse
ing to cvsweb, but that still doesn't tell me whether anyone is
_using_ it.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
48 sectors
wd1: 32-bit data port
wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
wd1: non-rotational device
wd1(piixide1:0:1): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
(2) Unless and until the functionality is standardized, it makes the
system gratuitously nonportable. ("Portable between what I think are
the currently most popular two compilers" is awfully weak, even if
"what I think" is correct.)
/~\ The ASCII
while(0) don't visually
disappear into the containing if-elseif construct.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
ion level, but that's the only change I would say needs making
there. With the current formatting, the do and while(0) tend to
visually disappear into the if control structure, making the contained
breaks too easy to misread.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Aga
LAPSE_RANGE is an example. While it would technically be
possible to make it fast and simple by taking advantage of the
granularity requirement leeway, such an implementation would be too
restrictive to be worth doing.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X
y require disabling all OS knowledge of
USB or something comparably drastic, which may or may not be an option
for your use case.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E
to the hardware. But it can help if
your issues manifest before that, and, even if not, you've narrowed
things down - and with care you may be able to map the hardware again.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal
ore
accurately, crawl - diskless.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
s occur to me that
having the underlying code available would make it more likely that
someone would pick it up in the future.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
g or crashing the system
while still preserving a useful system.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
oks like what I was looking for: something
that blocks until a git subprocess finishes without handling filesystem
requests in the meantime. I'll need to reorganize the code a little to
fix that.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML
ish could very well be in poll() waiting for
git to print output.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
useful information in case of another hang, that
is another story.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
Mouse
\ / Ribbon Campaign
X Against HTMLmo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
bozohttpd, those do not surprise me. At least half the hits I get
these days are fetching from the puffs mount (it's
/export/ftp/pub/mouse/git-unpacked; /export/ftp is also the root
directory used by bozohttpd.)
The git and one of the mailwrappers were at the end of the tstile wait
chains I found
Oh, and one thing I don't think I've said yet:
Thank you very much, everyone who's even thought about this issue!
I've seen at least two off-list emails already in addition to the
on-list ones.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTMLmo
o include PPID; in this last
hang, I would have liked to have known whether the git process were a
child of the gitfs process.
I will also take that "other system" I mentioned, make a puffs mount,
and then start playing that game. If I can get it to tstile in a
reasonable time frame, it
1 - 100 of 816 matches
Mail list logo