To check spamassassin and verify all required perl modules are installed
spamassassin -D –lint 2>&1 | grep -i failed
then use cpan install module::name ie
cpan install Digest::SHA1
Some additions are required to augment the default install. There is benefit
to adding missing modules as a more complete spam analysis will occur.
You can copy or backup all your databases with these commands including
coping to another server.
mysqldump -u root -p yourdb > mysqlbak.sql
or for dumping all databases
mysqldump –all-databases -u root -p > mysqlbakall.sql
mysql -u root -p yourdb < mysqlbak.sql
to restore all databases
mysql -u root -p < mysqlbakall.sql
It is simple to reset the Samsung S6. Sometimes this is necessary to improve battery life
and performance or just remove clutter from your phone.
First us Samsung’s excellent Smart Switch software (d/l from Samsung for Windows or OSX) and
backup your phone. The software backs up all your data including sms, email settings, etc.
It is very quick also.
Then do a hard reset by holding volume up key, home key, and power key with the phone
powered off. release the home key as soon as you see the Samsung logo and you should boot
into the recovery mode.
Then select from Recovery Mode menu “wipe data / factory reset” using Volume buttons to
navigate and Power button to confirm. After restarting your phone, connect backup to
your desktop and restore your phone with Smart Switch.
You find a few apps with setup requirements but it’s mostly painless.
After months of ownership and many experiments, I have found the best setup for battery life
on my S6-active was to change wifi-settings to enable wifi only while awake (#1 battery eater if
you enable wifi while sleeping) or if you don’t need/care about data usage, leave wifi off.
Also use android email app and only sync during most important part of day (settings has ability
to sync during specified hours) for your email. You can manually sync at other times.
If you take this approach, your S6 (or at least my S6-Active) shows 50+ hours standby after a full charge.
You can easily clone like routerboard hardware with these commands:
First to ssh admin@youripaddress or run terminal from winbox and run the following on the device you want to clone in this example we clone an rb751g to rb951.
## on rb751g type:
/export compact file=name
Then copy the name.rsc file to the rb951 $$either drag and drop it to files with winbox or use sftp.
hard reset the device you want to clone to by powering off and holding reset button, powering on,
and releasing reset button when led next to power plug starts to rapidly flash. Wait until the
os initializes and access with winbox.
## on rb951 type (after hard reset):
/import name.rsc ## you should see no errors.
## then on rb951 type:
/system reset run-after-reset=”name.rsc”
This will clear the current config and import the one from the rb751g
After a minute to load or so you should be able to access the rb951 with winbox and have a complete clone
of the rb751g.
To add serial access to your vm, with Debian/Ubuntu apt-get install libguestfs-tools.
Then with vm shutdown, execute the following:
root:~# guestmount -d vmname -i /mnt
root:~# ln -s /mnt/lib/systemd/system/getty@.service /mnt/etc/systemd/system
root:~# umount /mnt
Reboot your vm and you should have serial console access.
The dd utility is a good way to make a backup of your kvm vm image. It
is nice to have a progress indicator so install pv (pipe viewer) to
gain this feature ..ie apt-get install pv.
Here is a backup script:
dd if=org.img | pv | dd of=backup.img bs=1M
On my system it took about 10 minutes to complete a backup of a 50g image.
Postfix runs chrooted by default on most distributions. Jessie is no exception.
There are a couple of crucial modifications that are important and not well documented.
1) If you are running sasl, then this is the correct way to configure the chroot sasl
connection. Test your install first using testsaslauth -u [user] -p [password]. If you
get no connect or some other error you need the following additions.
rm -r /var/run/saslauthd/
mkdir -p /var/spool/postfix/var/run/saslauthd
ln -s /var/spool/postfix/var/run/saslauthd /var/run
chgrp sasl /var/spool/postfix/var/run/saslauthd
adduser postfix sasl
service postfix restart
service saslauthd restart
Then retest with testsaslauth you should get OK “Success.”
2) The cache files of postfix are also chrooted into the /var/spool/var/lib/postfix(chroot)
directory. If you do not see the cache files listed below in this directory, then
complete the following to correct the cache file locations.
The cache directory /var/lib/postfix contains:
master.lock, prng_exch, smtpd_scache.db, smtp_scache.db,and verify_cache.db.
To be safe copy these files and restore them to the new chrooted folder.
They will update after restarting postfix.
rm -r /var/lib/postfix
mkdir -p /var/spool/postfix/var/lib/postfix
ln -s /var/spool/postfix/var/lib/postfix /var/lib
chgrp postfix /var/spool/postfix/var/lib/postfix
chown -R postfix:postfix /var/spool/postfix/var/lib/
service postfix restart
You can test by running:
postmap -s btree:/var/lib/postfix/verify_cache
You should see no errors.