Ticket #34 (accepted enhancement)

Opened 14 years ago

Last modified 14 years ago

Die gracefully or print when database is not available

Reported by: jerome Owned by: jerome
Priority: major Milestone:
Component: pykota Version: development
Keywords: Cc:

Description (last modified by jerome) (diff)

When the cupspykota backend runs, we know that we need read+write access to the database. Introduce a printingwithnodb directive which allows either print or fail (and possibly ignore which is fail with an exit(0)), as values in pykota.conf. This directive will let PyKota know if it has to fail (as it does actually), or print anyway if the database isn't available.

Change History

Changed 14 years ago by jerome

  • status changed from new to accepted
  • description modified (diff)

Changed 14 years ago by jerome

  • description modified (diff)

Changed this to cover the case where no database is available at all : for example the database was manually shut down by the administrator but he forgot to disable printing as well. The ignore value may not be a good idea, and even with the print value at the very least a warning should be sent to the administrator.

Note: See TracTickets for help on using tickets.