| I have written a server program that listens on port 3000. The program
| works very well except for one feature. I am asking if that is normal,
| or whether I forgot something.
|
| If I run the program it does fine. If I then kill the program (after it
| has accepted connections), and then
| > Are there any plans of making gethostbyname_r() and gethostbyaddr_r()
| > available in FreeBSD? May be somebody already has them almost ready
| > to be commited? Or are there any considered wrong way to go?
| >
| > The reason I'm asking is that I actually have a local patch implementing
| >
| Is there a reason that ADNS won't work for this?
|
| http://www.chiark.greenend.org.uk/~ian/adns/
Technically, no. Morally, it's GNU. :-)
--
Man is a rational animal who always loses his temper when he is called
upon to act in accordance with the dictates of reason.
-- Osca
| i've just received confirmation from the author of the KAME resolution code
| that it isn't at all thread safe:
|
| >Sure. As noted in name6.c, thread related stuff is not implemented yet.
| >Since our resolver code based on bind4 doesn't aware thread safeness,
| >all I can do now would be o
| Indeed, Poul's idea has massive geek potential.
|
| However, for the geek impaired, there is always the 82802 Random
| Number Generator which is included on newer Intel chipsets. It may
| not be the holy grail of randomness, but nearly every PC will have
| one, and I think it'd be good if Fre
ad of going through pains of moving everything around, why not build
a static mt on the rescue disk only?
--
Dan Moschuk ([EMAIL PROTECTED])
"Don't get even -- get odd!"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Greetings,
I've got myself a bright new shiny Toshiba 4260 laptop, with one small
problem. I cannot seem to get the screen any bigger than a small window
(similiar to Fn + F on my Vaio).
Any ideas how I can get this full screen?
-Dan
--
Dan Moschuk ([EMAIL PROTECTED])
"Don't
d
| calls to gethost* to allow only 1 thread to call them at a time.
That won't work either, since, if I remember correctly, the returned
struct hostent is static.
-Dan
--
Dan Moschuk ([EMAIL PROTECTED])
"Waste not fresh tears on old griefs."
To Unsubscribe: send mail to [EMAIL P
snip. ]
When you compile standalone, do you use the same -W options as the kernel
does when it compiles? That may account for the millions of warnings you
getting when trying to build your driver with the regular kernel build.
Cheers,
--
Dan Moschuk ([EMAIL PROTECTED])
"Waste not fr
be
observed sending mail. Everything goes fine until after the DATA stage,
where we become stuck in the above retransmission loop.
Ideas?
--
Dan Moschuk ([EMAIL PROTECTED])
"Waste not fresh tears on old griefs."
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
to do with US export regulations I'm sure),
attacking the keyspace is quite trivial to do (about a complexity of
2^25).
Another interesting point is that with one player key compromised, one can
derive the rest of the player keys through a similar search.
--
Dan Moschuk ([EMAIL PROTECTED])
've taken this over from Cameron starting yesterday actually. I hope
to finish it in the next couple of weeks. When it's done, you can
expect a post. :-)
-Dan
--
Dan Moschuk ([EMAIL PROTECTED])
"Waste not fresh tears on old griefs."
To Unsubscribe: send mail to [EMAIL PR
thousand miles north! :-)
--
Dan Moschuk ([EMAIL PROTECTED])
"Cure for global warming: One giant heatsink and dual fans!"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
due to the
| patent restrictions on RSA.
The RSA patent makes things a lot more difficult. If we do add some crypto
into the kernel I suggest we use patent-free algorithms to start with.
--
Dan Moschuk ([EMAIL PROTECTED])
"Cure for global warming: One giant heatsink and dual fans!"
| I reviewed the NFSv4 specs recently and came to the same conclusion. To do
| it right will be quite a bit of work and would include a decent kernel
| side implementation of rpc and gssapi.
Cool! I can take that "I volunteer" ? :-)
--
Dan Moschuk ([EMAIL PROTECTED])
"Cure for
x27;d help see it into Darwin.
|
| BTW, is anyone working on NFS Version 4 for BSD? Rick?
A few of us talked about this on IRC a few weeks ago and it was decided that
when/if we implement NFSv4 it would have to be from scratch. A pretty big
task.
--
Dan Moschuk ([EMAIL PROTECTED])
"Cure for
ointer. What if
| "sd2=accept(sd, (struct sockaddr*)&cad, &alen)" gets
| executed before your previous serverstart() finishs "sd2 = *((int*)ptr)"?
Since accept isn't atomic, it would be best to enclose the whole sha-bang in
a mutex up until the sd2 = *((int *) ptr)
sd2 = (int*)ptr;
|
| dowhatever(sd2);
| }
|
| Any ideas as to what I'm doing wrong? Also, thanks for your help.
|
| Rob
Try this.
void *serverstart(void *ptr)
{
int sd2;
sd2 = *((int *) ptr);
...
}
--
Dan Moschuk ([EMAIL PROTECTED])
"Cure for global wa
l setup? Do you create a thread after
the accept call to handle the connection, or do you pre-spawn threads in a
pool?
If you allocate the socket descriptor for the client in the starting routine
for the thread, it should have its own copy.
--
Dan Moschuk ([EMAIL PROTECTED])
"Cure for glob
net card inserted
insert /etc/pccard_ether ep0
remove echo 3Com Megahertz Ethernet card removed
remove /sbin/ifconfig ep0 delete
the kernel config is a chopped down PCCARD
Cheers,
--
Dan Moschuk ([EMAIL PROTECTED])
"Cure for global warming: One giant heatsink and dual fa
; command to see what your allowed
openfiles are. You can raise this with ``unlimit''.
You will also want to look at a few kernel options if the above doesn't fix
it.
--
Dan Moschuk ([EMAIL PROTECTED])
"Try not. Do, or do not. There is no try."
that information from the
motherboard, and then some userland program to return it in the form of an SNMP
response.
So, unless you are prepared to dust off that C compiler, you're out of
luck.
--
Dan Moschuk ([EMAIL PROTECTED])
"Try not. Do, or do not.
it output a shell script that can be run
manually.
--
Dan Moschuk ([EMAIL PROTECTED])
"Try not. Do, or do not. There is no try."
-- Yoda
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
| } If no one has any objections, I'd like to start on this tomorrow.
|
| You might want to grab the latest BIND release from ftp.isc.org. One
| of the comments in the CHANGES file from a while ago is:
|
| 384. [feature] there is now a nearly-thread-safe resolver API, with
|
| > Yeah, that IS a horrible idea of mine. :) Changing the API should be a last
| > resort, though, since we don't want to introduce to many FreeBSDisms into
the
| > already-fragmented-enough Unix world.
| >
| > Just a thought, how does Linux's GNU libc handle gethostby* in threaded
apps?
|
|
| } If no one has any objections, I'd like to start on this tomorrow.
|
| You might want to grab the latest BIND release from ftp.isc.org. One
| of the comments in the CHANGES file from a while ago is:
|
| 384. [feature] there is now a nearly-thread-safe resolver API, with
|
| > Yeah, that IS a horrible idea of mine. :) Changing the API should be a last
| > resort, though, since we don't want to introduce to many FreeBSDisms into the
| > already-fragmented-enough Unix world.
| >
| > Just a thought, how does Linux's GNU libc handle gethostby* in threaded apps?
|
| P
| Well, I guess we might as well change the API, since everyone else does.
Unless
| someone comes up with a bettter idea, of course :)
|
| -Joe
The API should not change. There is already enough descrepency between UNIXs
to warrant programs like autoconf, we should not introduce another.
We sh
| Well, I guess we might as well change the API, since everyone else does. Unless
| someone comes up with a bettter idea, of course :)
|
| -Joe
The API should not change. There is already enough descrepency between UNIXs
to warrant programs like autoconf, we should not introduce another.
We sh
| >After quite an exhausting night (of all the ways I didn't want to spend my
| >Sunday...) I've managed to track down a problem that has been frustrating me
| >all night. The problem exists with multiple threads calling gethostbyaddr()
| >(not necessarily at the same time).
|
| src/lib/libc/n
| >After quite an exhausting night (of all the ways I didn't want to spend my
| >Sunday...) I've managed to track down a problem that has been frustrating me
| >all night. The problem exists with multiple threads calling gethostbyaddr()
| >(not necessarily at the same time).
|
| src/lib/libc/
Greetings,
After quite an exhausting night (of all the ways I didn't want to spend my
Sunday...) I've managed to track down a problem that has been frustrating me
all night. The problem exists with multiple threads calling gethostbyaddr()
(not necessarily at the same time).
Here's a debug out
Greetings,
After quite an exhausting night (of all the ways I didn't want to spend my
Sunday...) I've managed to track down a problem that has been frustrating me
all night. The problem exists with multiple threads calling gethostbyaddr()
(not necessarily at the same time).
Here's a debug ou
Greetings,
A machine that I hold very close under my wing has been very contently
chugging along for the last few months with practically no idle processor.
However, I noticed that the CPUs are spinning a lot of cycles in the
system area.
CPU states: 5.5% user, 0.0% nice, 88.9% system, 4.0%
I noticed on a very high traffic'd webserver, I have just over 4000 sockets
stuck in the TIME_WAIT state. Ideally, I want to "bend" the RFC a bit and
close the descriptor before it hits that state, or, ignore the 2MSL wait
when it enters that state.
I take it there is no sysctl switch to trigg
The machine is a SMP 3.0-RELEASE box.
A heavily threaded program is segfaulting in the longjmp() function.
Any ideas what would cause this?
Regards,
Dan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
| One of my plans is to merge all of these changes into our tree (along with all
| the other minor changes/manpage corrections, etc).
|
| Longer term, I'd like to work on porting some of their kernel code like
| randomized sin_port selection and TCP initial sequence numbering, probably
| hidden b
| ¿Have you considered PostgreSQL? It is on the ports collection, and is a
| heavy duty database engine, with transactions, subqueries (only partial
| support), etc. Version 6.5 will be released in about two weeks, and it
| adds MVCC (multi-version concurrency control), which will improve a lot
|
| > I'd like to stay away from the commercial database suites (i.e. Oracle) for
| > the time being, however I will eventually move to it once the database grows
| > to over 100M records. In the meantime however, I'm debating heavily between
| > MySQL and Berkeley DB with a multi-threaded socket f
Greetings,
I've taken up a project that will rely very heavily on remote database
access. Naturally, the choice as to which database engine to use is a
crucial one.
I'd like to stay away from the commercial database suites (i.e. Oracle) for
the time being, however I will eventually move to i
| You need to make sure that you are compiling against the right kernel
| headers. Not that I'm saying that you are, just making sure.
|
| Warner
Doh! Are my cheeks red.
After rebuilding /usr/include, and recompiling pccard all is well.
Thanks!
--
Dan Moschuk ([EMAIL PROTECTED])
i) make/make install usr.sbin/pccard
iii) copy new pccard.conf into place
iv) build and reboot new kernel
If I've forgotten a step, please let me know.
Thanks,
--
Dan Moschuk ([EMAIL PROTECTED])
"Cure for global warming: One giant heatsink and dual fans!"
To Unsubscribe: send mai
My 56k modem card
(3COm 3CC156 B) also fails with the exact error message.
--
Dan Moschuk ([EMAIL PROTECTED])
"Cure for global warming: One giant heatsink and dual fans!"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
43 matches
Mail list logo
