Wilko Bulte <[EMAIL PROTECTED]> writes:
> You have my symphaty, no-one ever gets Wilko right. And it is dead
> simple derivative of Willem Coenraad. Wilko. Not Wilco. Right?
Roger, wilco.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-s
On May 16, 2005, at 10:58 AM, Chris wrote:
> Dear Paul ...
I thought the canonical form was "Dear John"...
Jim Thompson <[EMAIL PROTECTED]> writes:
> No no no. The walrus was Paul.
Goo goo g'joob!
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
f
Damian Gerow <[EMAIL PROTECTED]> writes:
> Ack. I just noticed that 'pentiumpro' is also mis-spelled 'penitumpro' as
> well... PR time, I think.
No, that was fixed two months ago (rev 1.261)
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-
Damian Gerow <[EMAIL PROTECTED]> writes:
> I can understand listing nocona under AMD64 architecture, but isn't it an
> Intel CPU? Am I missing something in thinking it should be listed under
> "Intel CPUs"?
Correct. I pointed this out when the commit was made, but apparently
noone listened.
DES
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> 'k, I've been doing multiple since 7.2 on the same machine, all on the
> same port, all different IPs, all on 4.x servers ... have never had an
> issue with crashes (its pretty much my most stable 4.x server) ...
It was never possible. 8.0 has a ha
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> You've all lost me here ... what exactly is the problem?
You can't run multiple instances of PostgreSQL on the same machine
(even in chroot or jail, even without TCP/IP support) without changing
the port number in postgresql.conf. PostgreSQL create
Richard Coleman <[EMAIL PROTECTED]> writes:
> It might be easier to hack PostgreSQL so that the shared memory
> identifier depends not only on the port, but also on the IP address
> (which will of course be different for each jail). Or better yet, to
> be able to specify the shared memory identifi
An unknown poster wrote:
> AFAIR PostgreSQL generates the shared memory identifier based on
> the port it is runing on. It is possible to run two instances of
> PostgreSQL on different ports, so it should work if they are in
> seperate jails.
Correct.
Alexander Rusinov <[EMAIL PROTECTED]> writes:
Could somebody please test the attached patch on a recent RELENG_5?
It fixes a number of bugs in procfs and linprocfs; most notably, the
output of "ls /proc" (or "ls /compat/linux/proc") would be truncated
on systems with a largish number of processes (more than ~120).
There's a locking fix there t
