I've been trying to update this -current machine with the bsd.rd from
the last 4 snapshots,
the last being from "Sun Apr 26 02:22:08 MDT 2015".
However this kernel immediately after reporting how much ram I have
panics with this message:
fatal protection fault (4) in supervisor mode
trap type
Eivind Eide (2015-04-26 13:02 +0200):
> I've been trying to update this -current machine with the bsd.rd from the
> last 4 snapshots,
> the last being from "Sun Apr 26 02:22:08 MDT 2015".
> However this kernel immediately after reporting how much ram I have panics
> with this message:
>
> fatal pr
> Eivind Eide (2015-04-26 13:02 +0200):
> > I've been trying to update this -current machine with the bsd.rd from the
> > last 4 snapshots,
> > the last being from "Sun Apr 26 02:22:08 MDT 2015".
> > However this kernel immediately after reporting how much ram I have panics
> > with this message:
>
On Sun, Apr 26, 2015 at 01:02:49PM +0200, Eivind Eide wrote:
> I've been trying to update this -current machine with the bsd.rd
> from the last 4 snapshots,
> the last being from "Sun Apr 26 02:22:08 MDT 2015".
> However this kernel immediately after reporting how much ram I have
> panics with this
Hi, man ksh says:
RANDOM A random number generator. Every time RANDOM is referenced,
it is assigned the next random number in the range 0-32767.
By default, arc4random(3) is used to produce values. If the
variable RANDOM is assigned a valu
> Hi, man ksh says:
>
> RANDOM A random number generator. Every time RANDOM is referenced,
> it is assigned the next random number in the range 0-32767.
> By default, arc4random(3) is used to produce values. If the
> variable RANDOM is ass
Hi,
relayd is a nice software. I also used it once for* http and smtp purpose*
for zimbra backend servers. It was very fast. I was very happy about it.
But , suddenly I failed. My users complained. So I installed haproxy on
Centos. this haproxy has been running without any problems for nearly 300
7 matches
Mail list logo
