It's not recommended it's exposed to the world for that reason, it's recommended you protect the service via a firewall and configure Ice Secrets below. Note that all virtual servers share an Ice service, and without secrets configured anyone with access to the Ice port has full administrative access to every virtual server on the Murmur process. More information on configuring Ice Endpoints can be found in the ZeroC Ice documentation. Murmur supports extensive RPC via ZeroC Ice, and the ice setting specifies the "endpoint". It's really only useful if you have multiple Murmur processes that share the same D-Bus.ĭbusservice= This setting allows you to configure a distinct service name for this Murmur process on the D-Bus. To activate it simply uncomment the following line: It's poorly documented, new features aren't added to it, and it's possible it could be removed at some point in the future. Murmur has deprecated support for control via D-Bus. Murmur does its best to speak sensible, standards-compliant SQL - so you may have luck with any of the other database drivers supported by QSql - but note that SQLite is the most tested configuration followed very distantly behind by MySQL. The default is QSQLITE, which is the SQLite database driver. The database backend that Murmur will use for storage of persistent data. Other database drivers will use this setting for their own purposes -with QMYSQL it will set the database name. If dbDriver is QSQLITE (the default), this setting will specify the path to the database file. These options have different meanings depending on the database engine used, and explaining them is outside the scope of this document. There are other options not listed below, namely: dbUsername, dbPassword, dbHost, dbPrefix, dbOpts, and dbPort.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |