Subject | RE: [firebird-support] Tcp-wrapper support |
---|---|
Author | Rick Debay |
Post date | 2007-02-22T21:02:25Z |
> Given that you could have TCP wrapper functionality enabled if youused inetd or xitend, why wouldn't you consider using that approach for
launching FB?
Our database is not a network service. It will quite happily run doing
useful things (up to a point) if no one connects. So we want the
database to start even with no connections.
-----Original Message-----
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Leyne, Sean
Sent: Thursday, February 22, 2007 3:32 PM
To: firebird-support@yahoogroups.com
Subject: RE: [firebird-support] Tcp-wrapper support
Rick,
> > how do you launch Firebird?Given that you could have TCP wrapper functionality enabled if you used
>
> As a service at runlevels 2 through 5, and firebird's init script uses
> startproc to launch /opt/firebird/bin/fbguard.
inetd or xitend, why wouldn't you consider using that approach for
launching FB?
Sean
------------------------ Yahoo! Groups Sponsor --------------------~-->
Great things are happening at Yahoo! Groups. See the new email design.
http://us.click.yahoo.com/lOt0.A/hOaOAA/yQLSAA/67folB/TM
--------------------------------------------------------------------~->
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Visit http://www.firebirdsql.org and click the Resources item on the
main (top) menu. Try Knowledgebase and FAQ links !
Also search the knowledgebases at http://www.ibphoenix.com
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Yahoo! Groups - Join or create groups, clubs, forums & communities.
Links
Disclaimer: This message (including attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. RxStrategies, Inc. shall not be liable for the improper or incomplete transmission of the information contained in this communication or for any delay in its receipt or damage to your system. RxStrategies, Inc. does not guarantee that the integrity of this communication has been maintained nor that this communication is free from viruses, interceptions or interference.