Posts

Posted on

Secure Shell client(s) – various platform(s)

Posted on

World Wide Web Browser(s)

Posted on

Verizon Wireless Unlimited Data Plan GrandFathered

Important message regarding your bill.

Starting on November 15, 2015, we are increasing the price of each unlimited data feature by $20/mo. If any of your lines with an unlimited data feature are currently on a two-year contract, the increase will not begin until you complete your contract term or enter into a new one.

To learn more about your current usage and plan options, please call us at (800) 890-0084 or manage your plan and data usage anytime at vzw.com/myplan.

$ adb pull /system/build.prop
66 KB/s (4618 bytes in 0.068s)
$ grep ‘net.tethering.noprovisioning=true’ build.prop
$ echo ‘net.tethering.noprovisioning=true’ >> build.prop
$ tail -1 build.prop
net.tethering.noprovisioning=true
$ adb push build.prop /system
507 KB/s (4652 bytes in 0.008s)
$ adb reboot
$

Posted on

mysql database error table is marked as crashed and should be repaired

error:

XXXXXX XX:XX:XX [ERROR] /usr/libexec/mysqld: Table ‘./database/table’ is marked as crashed and should be repaired

myisamchk(1) – MyISAM table-maintenance utility

· –recover, -r

Do a repair that can fix almost any problem except unique keys that are not unique
(which is an extremely unlikely error with MyISAM tables). If you want to recover
a table, this is the option to try first. You should try –safe-recover only if
myisamchk reports that the table cannot be recovered using –recover. (In the
unlikely case that –recover fails, the data file remains intact.)

If you have lots of memory, you should increase the value of
myisam_sort_buffer_size.

· –safe-recover, -o

Do a repair using an old recovery method that reads through all rows in order and
updates all index trees based on the rows found. This is an order of magnitude
slower than –recover, but can handle a couple of very unlikely cases that
–recover cannot. This recovery method also uses much less disk space than
–recover. Normally, you should repair first using –recover, and then with
–safe-recover only if –recover fails.

If you have lots of memory, you should increase the value of key_buffer_size.

(re)solution:

# service mysqld stop

# for tbl in `grep ‘ERROR.*Table’ ~mysql/$HOSTNAME.err | awk -F\’ ‘{print $2}’` ; do myisamchk –recover $tbl ; done

# service mysqld start

Posted on

FCC / National Do Not Call Registry