Install cvsup:

# cd /usr/ports/net/cvsup-without-gui/
# make install

install fastest cvsup:

# cd /usr/ports/sysutils/fastest_cvsup/
# make install
# fastest_cvsup -c u

copy the default supfile to our own before editing.

# cp /usr/share/examples/cvsup/stable-supfile /etc/stable-supfile
# cp /usr/share/examples/cvsup/ports-supfile /etc/ports-supfile

edit both of them and change the

*default host=

to the fastest cvsup server from the “fastest cvsup”

then update the ports

# cvsup -L2 -g /etc/ports-supfile
# cvsup -L2 -g /etc/stable-supfile

Then i guess we try to build the world. see if something breaky.

# cd /usr/src
# make buildworld

Recompiled kernel. I have my own kernel called “MYSPARC2″. Yours might just be “GENERIC”

# cd /usr/src
# make buildkernel KERNCONF=MYSPARC2
# make installkernel KERNCONF=MYSPARC2

rebooted into single user mode then:

# mount -u /
# mount -a -t ufs
# swapon -a

Now you are ready to install the new world.

# cd /usr/src
# make installworld

After that was done, mergemaster to update your configs:

mergemaster -v

Then used portmaster to upgrade all of the ports.

# portmaster -a

Basically everything i know about BSD comes from or stems from something I’ve read at freebsdmadeeasy.com

source: http://www.freebsdmadeeasy.com/tutorials/freebsd/updating-freebsd-with-cvsup.php

./automysqlbackup.sh.2.5: Command not found.

To run it in FreeBSD, you need to edit a single line. Automysqlbackup.sh.2.5 is a bash script, and it references the path ‘/bin/sh’. In freebsd, bash is installed at ‘/usr/local/bin/bash.’ If you haven’t already, install bash:

pkg_add -r bash

Then all you have to do is edit automysqlbackup.sh.2.5. Look for

#!/bin/bash

and change it to

#!/usr/local/bin/bash

Now you should be able to launch it properly by running ‘./automysqlbackup.sh.2.5′. creating a symlink would probably work, but i like this better.

1. ntpdate. This is manual. To run a time sync manually, just run

ntpdate -b pool.ntp.org

You can replace pool.ntp.org with whatever you want. To tell it to run whenever the system is booted, add this to /etc/rc.conf:

ntpdate_enable="YES"
ntpdate_hosts="[your ntp server]"

This works, but if you don’t reboot often, could be unreliable.

2. ntdp. ntpd just runs all the time and keeps you nsync with internet time servers. You would want to use this for servers that you don’t reboot all the time. for this:

create an /etc/ntpd.conf file:

server pool.ntp.org
driftfile /etc/ntp.drift
logfile /var/log/ntpd.log

you can start ntpd manually:

ntpd

and/or add a startup entry for it in /etc/rc.conf:

ntpd_enable="YES"

I recommend setting up both of these on servers. Ntpdate will snap your system to a good point before you begin synchronizing with ntpd. ntpd by itself will take a lot longer to get you synced up.

http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html
fsck -p
mount -a -t ufs
make sure /var/crash is writable
savecore /var/crash /dev/ad0b
exit
exit to multi-user

FreeBSD does not automatically include a default my.cnf for MySQL. Instead, a set of sample configuration files can be found under /usr/local/share/mysql. These configuration files include my-small.cnf, my-medium.cnf, my-large.cnf, my-innodb-heavy-4G, and my-huge.cnf. The appropriate file can be copied and used as a template configuration by performing the following actions:
cd /usr/local/share/mysql/
cp /usr/local/share/mysq/mysql-large.cnf /etc/my.cnf
/usr/local/etc/rc.d/mysql-server restart

thanks to http://www.barik.net/archive/2008/05/26/114616/ for the tip. ]]> http://www.surlyjake.com/mysql/freebsd-mysql-configuration/feed/ 0 http://www.surlyjake.com/mysql/what-not-to-do-in-mysql-and-how-to-pick-up-the-pieces/?utm_source=rss&utm_medium=rss&utm_campaign=what-not-to-do-in-mysql-and-how-to-pick-up-the-pieces http://www.surlyjake.com/mysql/what-not-to-do-in-mysql-and-how-to-pick-up-the-pieces/#comments Wed, 17 Sep 2008 03:31:13 +0000 jacob http://www.surlyjake.com/?p=14 note to self… do NOT kill mysql processes from phpmyadmin’s control panel and force mysql to quit. Bad things happen. In this case, mysql wouldnt start again. InnoDB’s indexes, binary logs, etc. were all out of sync. The 20 page log explaining all the ways the DB couldn’t start is located in the DB’s data dir, which in my case was in /dbdisks/<hostname>.err.

To tell mysql to pick up the messy pieces and throw up whats left of your data, edit or create /etc/my.cnf and add this little line to the “[mysqld]” section:

innodb_force_recovery = 3


The command is talked aboot here the number is btw 1 and 6. bigger the number, the more drastic and desperate it is. I tried 4, and it pulled the tables with no data. 1 gave me nothing. but 3 let me start and mysqldump my database.

mysqldump -u root -p <dbname > /path/to/.sql/file


so once the dump was completed, i moved the db data directory, commented out the “innodb_force_recovery” line, and restarted the computer. At restart the db data dir was re-created by mysql. fresh and clean. this deletes EVERYTHING. even users. re-import the data with

mysql -u root <dbname> < /path/to/.sql/file


go ahead and create the users needed, and set root password again. There you go.