8.1.6) on 2.4.2 since the day it was released. No problems whatsoever.
I'd recommend consulting the Oracle docs as to what is screwed with your
rollback segments. I highly doubt this is Linux's fault.
- --
Stephen Clouse <[EMAIL PROTECTED]>
Senior Programmer, IQ Coordinator Project Lead
) on 2.4.2 since the day it was released. No problems whatsoever.
I'd recommend consulting the Oracle docs as to what is screwed with your
rollback segments. I highly doubt this is Linux's fault.
- --
Stephen Clouse [EMAIL PROTECTED]
Senior Programmer, IQ Coordinator Project Lead
The IQ Group, Inc
his is a bug.
You have failed to RTFM. There is no bug here.
http://www.linuxdoc.org/FAQ/Linux-FAQ/x1955.html#AEN2242
- --
Stephen Clouse <[EMAIL PROTECTED]>
Senior Programmer, IQ Coordinator Project Lead
The IQ Group, Inc. <http://www.theiqgroup.com/>
-BEGIN PGP SIGNATURE-
.
You have failed to RTFM. There is no bug here.
http://www.linuxdoc.org/FAQ/Linux-FAQ/x1955.html#AEN2242
- --
Stephen Clouse [EMAIL PROTECTED]
Senior Programmer, IQ Coordinator Project Lead
The IQ Group, Inc. http://www.theiqgroup.com/
-BEGIN PGP SIGNATURE-
Version: PGP 6.5.8
iQA
s threads. (And what happens
when the master process *is* the target?)
- --
Stephen Clouse <[EMAIL PROTECTED]>
Senior Programmer, IQ Coordinator Project Lead
The IQ Group, Inc. <http://www.theiqgroup.com/>
-BEGIN PGP SIGNATURE-
Version: PGP 6.5.8
iQA/AwUBOr2XDgOGqGs0PadnE
happens
when the master process *is* the target?)
- --
Stephen Clouse [EMAIL PROTECTED]
Senior Programmer, IQ Coordinator Project Lead
The IQ Group, Inc. http://www.theiqgroup.com/
-BEGIN PGP SIGNATURE-
Version: PGP 6.5.8
iQA/AwUBOr2XDgOGqGs0PadnEQK0rACfQELDid11+m90bS/DrGyrsHW45ZEAn19G
e routine) and decides it needs just a pinch more memory
than what's available -- ick. 2.2.x doesn't appear to enforce new memory
allocation with a sniper rifle -- the new process just suffers a pleasant ("Out
of memory!") or violent (SIGSEGV) death.
- --
Stephen Clouse <[EMAIL PROTECTED]&
day getting intimate with
the backup files, since SIGKILLing random Oracle processes, as you might have
guessed, has a tendency to rape the entire database.
It would be nice to give immunity to certain uids, or better yet, just turn the
damn thing off entirely. I've already hacked that in...errr, out.
ing random Oracle processes, as you might have
guessed, has a tendency to rape the entire database.
It would be nice to give immunity to certain uids, or better yet, just turn the
damn thing off entirely. I've already hacked that in...errr, out.
- --
Stephen Clouse [EMAIL PROTECTED]
Senior Prog
) and decides it needs just a pinch more memory
than what's available -- ick. 2.2.x doesn't appear to enforce new memory
allocation with a sniper rifle -- the new process just suffers a pleasant ("Out
of memory!") or violent (SIGSEGV) death.
- --
Stephen Clouse [EMAIL PROTECTED]
Senior Prog
We have a development SMP machine which runs a myriad of server applications for
our development purposes -- Apache, Oracle, several others. Under 2.4.0 the
machine locks up, seemingly at random. Usually it simply stops responding
without fanfare -- you can, oddly enough, switch consoles with
We have a development SMP machine which runs a myriad of server applications for
our development purposes -- Apache, Oracle, several others. Under 2.4.0 the
machine locks up, seemingly at random. Usually it simply stops responding
without fanfare -- you can, oddly enough, switch consoles with
12 matches
Mail list logo