databases/mariadb55-server fails to package with oqgraph option
Beeblebrox
zaphod at berentweb.com
Sat May 31 08:44:41 UTC 2014
>After doing all of this your my.cnf id empty (unless you tune more, which
>usually makes sense on a production system) and your /etc/rc.conf contains:
>mysql_enable="YES"
>mysql_limits="YES"
>mysql_pidfile="/var/run/mysqld/mysqld.pid"
>mysql_args="--skip-innodb --socket=/var/run/mysqld/mysqld.sock
--log-error=/var/log/mysql.log"
That's beautiful man, thanks!
* What does "mysql_limits=YES" do?
* What is Mutex vs Spinlock? As I understand, one is older (thus slower)
than the other? Is the question pointless if not using InnoDB?
* Disabling InooDB did not work as planned (failed to start, log below). It
also re-created <aria_log.00000001 \ aria_log_control> despite having
deleted those files. Should I just leave InnoDB alone? If so, does it make
any sense to redirect the InnoDB-related files to a restricted / more
protected folder?
mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
[Note] Plugin 'InnoDB' is disabled.
[ERROR] Unknown/unsupported storage engine: InnoDB
[ERROR] Aborting
[Note] /usr/local/libexec/mysqld: Shutdown complete
mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
Thanks again & Regards.
-----
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: http://freebsd.1045724.n5.nabble.com/databases-mariadb55-server-fails-to-package-with-oqgraph-option-tp5916414p5916642.html
Sent from the freebsd-ports mailing list archive at Nabble.com.
More information about the freebsd-ports
mailing list