- Description has changed:
Diff:
~~~~
--- old
+++ new
@@ -1,6 +1,29 @@
If the PBE encounters a fatal problem during the creation of the temporary
database file, then it should unlink that file before exiting.
-If the PBE crashes it will still not do this, so it should also cleanup
+If the PBE crashes it may still not do this, so it could also cleanup
at start/restart. All imm.db tmp files are processor local, so it should
-be safe to remove all of them.
+in principle be safe to remove all of them. At least in normal deployments.
+
+However, I have decided not to implement such a cleanup at PBE re-start for
+the following reasons:
+
+ 1) The /tmp directory is shared with an unknown set of applications and
+ removing all files according to a pattern, where components of the
+ pattern are configurable strings, could be risky. That is, it could
+ possibly remove files not created by the PBE.
+
+ 2) The major problem was the omitted cleanup of temporary imm.db.XXXX files
+ and temporary imm.db.XXXX-journal files, dropped at *controlled* PBE
exit.
+ This was the problem that originated this ticket and this will be fixed
+ by this ticket.
+
+ 3) Uncontrolled crashes of the PBE are rare. Uncontrolled crashes during
+ generation of the imm.db file (during which the tmp file exists) are
+ rarer. Cyclic uncontrolled crashes during generation of the imm.db file
+ are even rarer and should never happen in a production system.
+
+ 4) Should it be the case that some deployment does have problems with
+ dropped /tmp/imm.db.XXXX files even after the fix (2) of this ticket
+ then a new ticket could be written.
+
~~~~
---
** [tickets:#869] IMM: PBE must unlink any /tmp/imm.db.xxxx file when exiting
on error**
**Status:** accepted
**Milestone:** future
**Created:** Tue Apr 22, 2014 01:55 PM UTC by Anders Bjornerstedt
**Last Updated:** Wed Apr 30, 2014 07:30 AM UTC
**Owner:** Anders Bjornerstedt
If the PBE encounters a fatal problem during the creation of the temporary
database file, then it should unlink that file before exiting.
If the PBE crashes it may still not do this, so it could also cleanup
at start/restart. All imm.db tmp files are processor local, so it should
in principle be safe to remove all of them. At least in normal deployments.
However, I have decided not to implement such a cleanup at PBE re-start for
the following reasons:
1) The /tmp directory is shared with an unknown set of applications and
removing all files according to a pattern, where components of the
pattern are configurable strings, could be risky. That is, it could
possibly remove files not created by the PBE.
2) The major problem was the omitted cleanup of temporary imm.db.XXXX files
and temporary imm.db.XXXX-journal files, dropped at *controlled* PBE exit.
This was the problem that originated this ticket and this will be fixed
by this ticket.
3) Uncontrolled crashes of the PBE are rare. Uncontrolled crashes during
generation of the imm.db file (during which the tmp file exists) are
rarer. Cyclic uncontrolled crashes during generation of the imm.db file
are even rarer and should never happen in a production system.
4) Should it be the case that some deployment does have problems with
dropped /tmp/imm.db.XXXX files even after the fix (2) of this ticket
then a new ticket could be written.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
