Debian – BAFM

Linux NAS optimizations

July 9, 2014July 10, 2014 Christian Leave a comment

Well, I recently had to flatten my archive NAS (well only the OS part … *wheeeh*). Since I didn’t have the chance to backup the old settings I had to do everything from scratch … And this time I decided, I wasn’t doing a script but rather the proper way.

I spent a while reading through the Internetz about the various settings until I stumbled upon a Frauenhofer Wiki entry. From there I ended up writing those udev-rules and the sysctl configs…

# Settings from http://www.fhgfs.com/wiki/StorageServerTuning

# Set an appropriate IO scheduler for file servers.
KERNEL=="sd[a-z]", ATTR{queue/scheduler}="deadline"
KERNEL=="sd[a-i][a-z]", ATTR{queue/scheduler}="deadline"

# Give the IO scheduler more flexibility by increasing the number of
# schedulable requests.
KERNEL=="sd[a-z]", ATTR{queue/nr_requests}="4096"
KERNEL=="sd[a-i][a-z]", ATTR{queue/nr_requests}="4096"

# To improve throughput for sequential reads, increase the maximum amount of
# read-ahead data. The actual amount of read-ahead is adaptive, so using a
#  high value here won't harm performance for small random access.
KERNEL=="sd[a-z]", ATTR{queue/read_ahead_kb}="73728"
KERNEL=="sd[a-i][a-z]", ATTR{queue/read_ahead_kb}="73728"
KERNEL=="sd[a-z]", RUN+="/sbin/blockdev --setra 73728 /dev/%n"
KERNEL=="sd[a-i][a-z]", RUN+="/sbin/blockdev --setra 73728 /dev/%n"

SUBSYSTEM=="block", KERNEL=="md[0-9]*", RUN+="/sbin/blockdev --setra 663552 /dev/%n"
SUBSYSTEM=="block", KERNEL=="md[0-9]*", ATTR{md/stripe_cache_size}="9216"

# Optimal performance for hardware RAID systems often depends on large IOs
# being sent to the device in a single large operation. Please refer to your
# hardware storage vendor for the corresponding optimal size of
# /sys/block/sdX/max_sectors_kb.
# It is typically good if this size can be increased to at least match your
# RAID stripe set size (i.e. chunk_size x number_of_disks):
KERNEL=="sd[a-z]", ATTR{queue/max_sectors_kb}="512"
KERNEL=="sd[a-i][a-z]", ATTR{queue/max_sectors_kb}="512"

KERNEL=="sd[a-z]", ATTR{device/queue_depth}="1"
KERNEL=="sd[a-i][a-z]", ATTR{device/queue_depth}="1"

# Settings from http://www.fhgfs.com/wiki/StorageServerTuning

# Set an appropriate IO scheduler for file servers.

KERNEL=="sd[a-z]", ATTR{queue/scheduler}="deadline"

KERNEL=="sd[a-i][a-z]", ATTR{queue/scheduler}="deadline"

# Give the IO scheduler more flexibility by increasing the number of

# schedulable requests.

KERNEL=="sd[a-z]", ATTR{queue/nr_requests}="4096"

KERNEL=="sd[a-i][a-z]", ATTR{queue/nr_requests}="4096"

# To improve throughput for sequential reads, increase the maximum amount of

# read-ahead data. The actual amount of read-ahead is adaptive, so using a

# high value here won't harm performance for small random access.

KERNEL=="sd[a-z]", ATTR{queue/read_ahead_kb}="73728"

KERNEL=="sd[a-i][a-z]", ATTR{queue/read_ahead_kb}="73728"

KERNEL=="sd[a-z]", RUN+="/sbin/blockdev --setra 73728 /dev/%n"

KERNEL=="sd[a-i][a-z]", RUN+="/sbin/blockdev --setra 73728 /dev/%n"

SUBSYSTEM=="block", KERNEL=="md[0-9]*", RUN+="/sbin/blockdev --setra 663552 /dev/%n"

SUBSYSTEM=="block", KERNEL=="md[0-9]*", ATTR{md/stripe_cache_size}="9216"

# Optimal performance for hardware RAID systems often depends on large IOs

# being sent to the device in a single large operation. Please refer to your

# hardware storage vendor for the corresponding optimal size of

# /sys/block/sdX/max_sectors_kb.

# It is typically good if this size can be increased to at least match your

# RAID stripe set size (i.e. chunk_size x number_of_disks):

KERNEL=="sd[a-z]", ATTR{queue/max_sectors_kb}="512"

KERNEL=="sd[a-i][a-z]", ATTR{queue/max_sectors_kb}="512"

KERNEL=="sd[a-z]", ATTR{device/queue_depth}="1"

KERNEL=="sd[a-i][a-z]", ATTR{device/queue_depth}="1"

# Settings taken from http://www.fhgfs.com/wiki/StorageServerTuning

# To avoid long IO stalls (latencies) for write cache flushing in a production
# environment with very different workloads, you will typically want to limit
# the kernel dirty (write) cache size.

vm.dirty_background_ratio = 5
vm.dirty_ratio = 10

# Assigning slightly higher priority to inode caching helps to avoid disk seeks
# for inode loading
vm.vfs_cache_pressure = 50

# Buffering of file system data requires frequent memory allocation. Raising the
# amount of reserved kernel memory will enable faster and more reliable memory
# allocation in critical situations. Raise the corresponding value to 64MB if
# you have less than 8GB of memory, otherwise raise it to at least 256MB
vm.min_free_kbytes = 262144

# Settings taken from http://www.fhgfs.com/wiki/StorageServerTuning

# To avoid long IO stalls (latencies) for write cache flushing in a production

# environment with very different workloads, you will typically want to limit

# the kernel dirty (write) cache size.

vm.dirty_background_ratio = 5

vm.dirty_ratio = 10

# Assigning slightly higher priority to inode caching helps to avoid disk seeks

# for inode loading

vm.vfs_cache_pressure = 50

# Buffering of file system data requires frequent memory allocation. Raising the

# amount of reserved kernel memory will enable faster and more reliable memory

# allocation in critical situations. Raise the corresponding value to 64MB if

# you have less than 8GB of memory, otherwise raise it to at least 256MB

vm.min_free_kbytes = 262144

For now, I’m rather pleased with the results …

root:(charon.ka.heimdaheim.de) PWD:/
Wed Jul 09, 15:02:08 [0] > mdadm --detail /dev/md127
/dev/md127:
        Version : 1.2
  Creation Time : Sat Jan 26 18:35:19 2013
     Raid Level : raid5
     Array Size : 15626121216 (14902.23 GiB 16001.15 GB)
  Used Dev Size : 1953265152 (1862.78 GiB 2000.14 GB)
   Raid Devices : 9
  Total Devices : 10
    Persistence : Superblock is persistent

    Update Time : Wed Jul  9 15:03:28 2014
          State : clean
 Active Devices : 9
Working Devices : 10
 Failed Devices : 0
  Spare Devices : 1

         Layout : left-symmetric
     Chunk Size : 512K

           Name : charon:aggr1  (local to host charon)
           UUID : 6d11820f:04847070:2725c434:9ee39718
         Events : 11186

    Number   Major   Minor   RaidDevice State
       0       8      129        0      active sync   /dev/sdi1
       1       8       33        1      active sync   /dev/sdc1
       2       8       49        2      active sync   /dev/sdd1
       4       8       65        3      active sync   /dev/sde1
       5       8       17        4      active sync   /dev/sdb1
      10       8       97        5      active sync   /dev/sdg1
       9       8       81        6      active sync   /dev/sdf1
       8       8      161        7      active sync   /dev/sdk1
       7       8      145        8      active sync   /dev/sdj1

       6       8      113        -      spare   /dev/sdh1

root:(charon.ka.heimdaheim.de) PWD:/

Wed Jul 09, 15:02:08 [0] > mdadm --detail /dev/md127

/dev/md127:

Version : 1.2

Creation Time : Sat Jan 26 18:35:19 2013

Raid Level : raid5

Array Size : 15626121216 (14902.23 GiB 16001.15 GB)

Used Dev Size : 1953265152 (1862.78 GiB 2000.14 GB)

Raid Devices : 9

Total Devices : 10

Persistence : Superblock is persistent

Update Time : Wed Jul 9 15:03:28 2014

State : clean

Active Devices : 9

Working Devices : 10

Failed Devices : 0

Spare Devices : 1

Layout : left-symmetric

Chunk Size : 512K

Name : charon:aggr1 (local to host charon)

UUID : 6d11820f:04847070:2725c434:9ee39718

Events : 11186

Number Major Minor RaidDevice State

0 8 129 0 active sync /dev/sdi1

1 8 33 1 active sync /dev/sdc1

2 8 49 2 active sync /dev/sdd1

4 8 65 3 active sync /dev/sde1

5 8 17 4 active sync /dev/sdb1

10 8 97 5 active sync /dev/sdg1

9 8 81 6 active sync /dev/sdf1

8 8 161 7 active sync /dev/sdk1

7 8 145 8 active sync /dev/sdj1

6 8 113 - spare /dev/sdh1

And here’s the dd output:

root:(charon.ka.heimdaheim.de) PWD:/
Wed Jul 09, 14:57:32 [0] > dd if=/dev/zero of=/srv/smb/tmp bs=1G count=100 \
   oflag=direct
100+0 records in
100+0 records out
107374182400 bytes (107 GB) copied, 257.341 s, 417 MB/s

root:(charon.ka.heimdaheim.de) PWD:/

Wed Jul 09, 14:57:32 [0] > dd if=/dev/zero of=/srv/smb/tmp bs=1G count=100 \

oflag=direct

100+0 records in

100+0 records out

107374182400 bytes (107 GB) copied, 257.341 s, 417 MB/s

sa-learn, dovecot virtual users and virtual user configs

June 19, 2013June 21, 2013 Christian 2 Comments

Well, I wanted independent SpamAssassin Bayes databases per user (different users, different preferences). For that, RoundCube already set up the Junk folder. However, I wanted the ability (for myself, as well for my other users) to individually mark messages as either Spam or Ham.

Now, as I said before I wanted a trivial way to mark messages as Spam or Ham (without using the command line each time).

Now, that was the mailbox setup part. Now we do have to do some command line foo (yeah, it’s still necessary) to actually learn the mails as spam or ham. First we need a script, which scans the Maildir for each domain/user separately, and then creates the bayes database.

#!/bin/bash

# Script, which allows per-user bayes db's for a dovecot virtual user
# setup. sa-learn parses a set amount of folders (.Junk.Spam and .Junk.Ham) for
# Ham/Spam and adds it to the per-user db.

MAIL_DIR=/var/mail
SPAMASS_DIR=/var/lib/spamassassin
SPAM_FOLDER=".Junk.Spam"
HAM_FOLDER=".Junk.Ham"

# get all mail accounts
for domain in $MAIL_DIR/*; do
        for user in $MAIL_DIR/${domain##*/}/*; do
                mailaccount=${user##*/}
                dbpath=$SPAMASS_DIR/${domain##*/}/$mailaccount
                spamfolder=${domain}/${mailaccount}/Maildir/$SPAM_FOLDER
                hamfolder=${domain}/${mailaccount}/Maildir/$HAM_FOLDER

                if [ -d $spamfolder ] ; then
                        [ ! -d $dbpath ] && mkdir -p ${dbpath}
                        echo "Learning Spam from ${spamfolder} for user ${mailaccount}"
                        nice sa-learn --spam --dbpath ${dbpath}/bayes 
                                --no-sync ${spamfolder}
                fi

                if [ -d $hamfolder ] ; then
                        echo "Learning Ham from ${hamfolder} for user ${mailaccount}"
                        nice sa-learn --ham --dbpath ${dbpath}/bayes 
                                --no-sync ${hamfolder}
                fi

                if [ -d $spamfolder -o -d $hamfolder ] ; then
                        nice sa-learn --sync --dbpath $dbpath

                        # Fix dbpath permissions
                        chown -R mail.mail ${dbpath}
                        chmod 700 ${dbpath}
                fi
        done
done

#!/bin/bash

# Script, which allows per-user bayes db's for a dovecot virtual user

# setup. sa-learn parses a set amount of folders (.Junk.Spam and .Junk.Ham) for

# Ham/Spam and adds it to the per-user db.

MAIL_DIR=/var/mail

SPAMASS_DIR=/var/lib/spamassassin

SPAM_FOLDER=".Junk.Spam"

HAM_FOLDER=".Junk.Ham"

# get all mail accounts

for domain in $MAIL_DIR/*; do

for user in $MAIL_DIR/${domain##*/}/*; do

mailaccount=${user##*/}

dbpath=$SPAMASS_DIR/${domain##*/}/$mailaccount

spamfolder=${domain}/${mailaccount}/Maildir/$SPAM_FOLDER

hamfolder=${domain}/${mailaccount}/Maildir/$HAM_FOLDER

if [ -d $spamfolder ] ; then

[ ! -d $dbpath ] && mkdir -p ${dbpath}

echo "Learning Spam from ${spamfolder} for user ${mailaccount}"

nice sa-learn --spam --dbpath ${dbpath}/bayes

--no-sync ${spamfolder}

if [ -d $hamfolder ] ; then

echo "Learning Ham from ${hamfolder} for user ${mailaccount}"

nice sa-learn --ham --dbpath ${dbpath}/bayes

--no-sync ${hamfolder}

if [ -d $spamfolder -o -d $hamfolder ] ; then

nice sa-learn --sync --dbpath $dbpath

# Fix dbpath permissions

chown -R mail.mail ${dbpath}

chmod 700 ${dbpath}

done

This script is based on work from nesono and workaround.org. Anyhow, the script will scan each user folder (you might need to adjust the MAIL_DIR and SPAMASS_DIR variable, depending on where your MAIL_DIR is located.

Next, we need to adjust the SPAMD options to use the virtual-config-dir (that’s the SPAMD name for this).

--- spamassassin.orig   2013-06-19 19:49:30.000000000 +0200
+++ spamassassin        2013-06-19 19:18:07.000000000 +0200
@@ -14,7 +14,7 @@
 # make sure --max-children is not set to anything higher than 5,
 # unless you know what you're doing.

-OPTIONS="--create-prefs --max-children 5 --helper-home-dir"
+OPTIONS="--create-prefs --max-children 5 --helper-home-dir --virtual-config-dir=/var/lib/spamassassin/%d/%l -x -u mail"

 # Pid file
 # Where should spamd write its PID to file? If you use the -u or

--- spamassassin.orig 2013-06-19 19:49:30.000000000 +0200

+++ spamassassin 2013-06-19 19:18:07.000000000 +0200

@@ -14,7 +14,7 @@

# make sure --max-children is not set to anything higher than 5,

# unless you know what you're doing.

-OPTIONS="--create-prefs --max-children 5 --helper-home-dir"

+OPTIONS="--create-prefs --max-children 5 --helper-home-dir --virtual-config-dir=/var/lib/spamassassin/%d/%l -x -u mail"

# Pid file

# Where should spamd write its PID to file? If you use the -u or

As you can see, I basically appended the following to the OPTIONS variable: –virtual-config-dir=/var/lib/spamassassin/%d/%l -x -u mail

Now, here’s a couple of pointers:

–virtual-config-dir=pattern
This option specifies where per-user preferences can be found for virtual users, for the -x switch. The pattern is used as a base pattern for the directory name. Any of the
following escapes can be used:

%u — replaced with the full name of the current user, as sent by spamc.
%l — replaced with the ‘local part’ of the current username. In other words, if the username is an email address, this is the part before the “@” sign.
%d — replaced with the ‘domain’ of the current username. In other words, if the username is an email address, this is the part after the “@” sign.
%% — replaced with a single percent sign (%).

-u username, –username=username
Run as the named user. If this option is not set, the default behaviour is to setuid() to the user running “spamc”, if “spamd” is running as root.

Note: “–username=root” is not a valid option. If specified, “spamd” will exit with a fatal error on startup.

Now, only a small adjustment is still needed. In order for the inbound mails to be scanned with the per-user db’s, you need to adjust postfix’s master.cf file, to run spamc with the per-user db.

--- master.cf.orig      2013-06-19 19:56:57.000000000 +0200
+++ master.cf   2013-06-19 19:57:09.000000000 +0200
@@ -115,7 +115,7 @@

 # dovecot mail delivery
 dovecot   unix  -       n       n       -       -       pipe
-  flags=DRhu user=vmail:mail argv=/usr/lib/dovecot/deliver -d ${recipient}
+  flags=DRhu user=vmail:mail argv=/usr/bin/spamc -u ${recipient} -e /usr/lib/dovecot/deliver -f ${sender} -d ${recipient}

 amavis unix    -       -       -       -       2       smtp
         -o smtp_data_done_timeout=1200

--- master.cf.orig 2013-06-19 19:56:57.000000000 +0200

+++ master.cf 2013-06-19 19:57:09.000000000 +0200

@@ -115,7 +115,7 @@

# dovecot mail delivery

dovecot unix - n n - - pipe

- flags=DRhu user=vmail:mail argv=/usr/lib/dovecot/deliver -d ${recipient}

+ flags=DRhu user=vmail:mail argv=/usr/bin/spamc -u ${recipient} -e /usr/lib/dovecot/deliver -f ${sender} -d ${recipient}

amavis unix - - - - 2 smtp

-o smtp_data_done_timeout=1200

After that’s done (and a restart of postfix, spamassassin and dovecot) you should be the proud owner of a per-user dovecot/postfix/spamassassin implementation.

Tiny Tiny RSS init-script for multiple instances on Debian Wheezy

June 19, 2013June 19, 2013 Christian 2 Comments

Well, I have a bunch of Tiny Tiny RSS instances running on my webhost, and I wanted a init-script that starts the update-daemons for all instances.

Now, there’s already a bunch of init scripts for Debian around (1, 2) however none of them were to my liking or did what I wanted it to do. So I ended up (yeah, I know *again*) rewriting them.

#!/bin/sh
### BEGIN INIT INFO
# Provides:          ttrss
# Required-Start:    $local_fs $remote_fs networking
# Required-Stop:     $local_fs $remote_fs
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Tiny Tiny RSS update daemon
# Description:       Update the Tiny Tiny RSS subscribed syndication feeds.
### END INIT INFO

set -e

PATH=/sbin:/usr/sbin:/bin:/usr/bin
DESC="Tiny Tiny RSS update daemon"
NAME=$(command basename "${0}")

DISABLED=1
FORKING=0

# Read configuration variable file if it is present
[ -r "/etc/default/${NAME}" ] && . "/etc/default/${NAME}"

DAEMON_SCRIPT="update.php --daemon"

if [ $FORKING -ne 0 ] ; then
        DAEMON_SCRIPT="update_daemon2.php"
fi

DAEMON=/usr/bin/php

# Exit if the package is not installed
[ -x "$DAEMON" ] || exit 0

[ -d "${TTRSS_PATH}" ] || exit 0

# Load the VERBOSE setting and other rcS variables
. /lib/init/vars.sh

# Define LSB log_* functions.
# Depend on lsb-base (>= 3.0-6) to ensure that this file is present.
. /lib/lsb/init-functions

if [ "$DISABLED" != "0" -a "$1" != "stop" ]; then
        log_warning_msg "Not starting $DESC - edit /etc/default/tt-rss and change DISABLED to be 0.";
        exit 0;
fi

# Function that starts the daemon/service
do_start()
{
        for dir in ${TTRSS_PATH}/*; do
                INSTANCE_NAME=${dir##*/}
                start-stop-daemon --start --make-pidfile --background --quiet 
                        --chuid "${TTRSS_USERID}" --group "${TTRSS_GROUPID}" 
                        --chdir "${dir}" 
                        --pidfile "${TTRSS_PIDDIR}/ttrss-${INSTANCE_NAME}.pid" 
                        --exec "${DAEMON}" --test >/dev/null 
                        || return 1

                start-stop-daemon --start --make-pidfile --background --quiet 
                        --chuid "${TTRSS_USERID}" --group "${TTRSS_GROUPID}" 
                        --chdir "${dir}" 
                        --pidfile "${TTRSS_PIDDIR}/ttrss-${INSTANCE_NAME}.pid" 
                        --exec "${DAEMON}" -- ${dir}/${DAEMON_SCRIPT} --log 
                        /var/log/ttrss/${INSTANCE_NAME}.log 
                        || return 2
        done
}

# Function that stops the daemon/service
do_stop()
{
        for dir in ${TTRSS_PATH}/*; do
                INSTANCE_NAME=${dir##*/}
                start-stop-daemon --stop --make-pidfile --quiet 
                        --retry=TERM/1/KILL/5 
                        --pidfile "${TTRSS_PIDDIR}/ttrss-${INSTANCE_NAME}.pid" 

                RETVAL="$?"
                [ "$RETVAL" = 2 ] && return 2

                start-stop-daemon --stop --quiet --oknodo --retry=0/1/KILL/5 
                        --exec ${DAEMON}

                [ "$?" = 2 ] && return 2
                rm -f "${TTRSS_PIDDIR}/ttrss-${INSTANCE_NAME}.pid"
                return $RETVAL
        done
}


case "$1" in
        start)
                log_daemon_msg "Starting $DESC" "$NAME"
                do_start
                case "$?" in
                        0|1) log_end_msg 0 ;;
                        2) log_end_msg 1 ;;
                esac
                ;;
        stop)
                log_daemon_msg "Stopping $DESC" "$NAME"
                do_stop
                case "$?" in
                        0|1) log_end_msg 0 ;;
                        2) log_end_msg 1 ;;
                esac
                ;;
        restart|force-reload)
                # If the "reload" option is implemented then remove the
                # 'force-reload' alias
                log_daemon_msg "Restarting $DESC" "$NAME"
                do_stop
                case "$?" in
                        0|1)
                                do_start
                                case "$?" in
                                        0) log_end_msg 0 ;;
                                        1) log_end_msg 1 ;; # Old process is still running
                                        *) log_end_msg 1 ;; # Failed to start
                                esac
                                ;;
                        *)
                                # Failed to stop
                                log_end_msg 1
                                ;;
                esac
                ;;
        *)
                echo "Usage: ${NAME} {start|stop|restart|force-reload}" >&2
                exit 3
                ;;
esac

:

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

#!/bin/sh

### BEGIN INIT INFO

# Provides: ttrss

# Required-Start: $local_fs $remote_fs networking

# Required-Stop: $local_fs $remote_fs

# Default-Start: 2 3 4 5

# Default-Stop: 0 1 6

# Short-Description: Tiny Tiny RSS update daemon

# Description: Update the Tiny Tiny RSS subscribed syndication feeds.

### END INIT INFO

set -e

PATH=/sbin:/usr/sbin:/bin:/usr/bin

DESC="Tiny Tiny RSS update daemon"

NAME=$(command basename "${0}")

DISABLED=1

FORKING=0

# Read configuration variable file if it is present

[ -r "/etc/default/${NAME}" ] && . "/etc/default/${NAME}"

DAEMON_SCRIPT="update.php --daemon"

if [ $FORKING -ne 0 ] ; then

DAEMON_SCRIPT="update_daemon2.php"

DAEMON=/usr/bin/php

# Exit if the package is not installed

[ -x "$DAEMON" ] || exit 0

[ -d "${TTRSS_PATH}" ] || exit 0

# Load the VERBOSE setting and other rcS variables

. /lib/init/vars.sh

# Define LSB log_* functions.

# Depend on lsb-base (>= 3.0-6) to ensure that this file is present.

. /lib/lsb/init-functions

if [ "$DISABLED" != "0" -a "$1" != "stop" ]; then

log_warning_msg "Not starting $DESC - edit /etc/default/tt-rss and change DISABLED to be 0.";

exit 0;

# Function that starts the daemon/service

do_start()

{

for dir in ${TTRSS_PATH}/*; do

INSTANCE_NAME=${dir##*/}

start-stop-daemon --start --make-pidfile --background --quiet

--chuid "${TTRSS_USERID}" --group "${TTRSS_GROUPID}"

--chdir "${dir}"

--pidfile "${TTRSS_PIDDIR}/ttrss-${INSTANCE_NAME}.pid"

--exec "${DAEMON}" --test >/dev/null

|| return 1

start-stop-daemon --start --make-pidfile --background --quiet

--chuid "${TTRSS_USERID}" --group "${TTRSS_GROUPID}"

--chdir "${dir}"

--pidfile "${TTRSS_PIDDIR}/ttrss-${INSTANCE_NAME}.pid"

--exec "${DAEMON}" -- ${dir}/${DAEMON_SCRIPT} --log

/var/log/ttrss/${INSTANCE_NAME}.log

|| return 2

done

}

# Function that stops the daemon/service

do_stop()

{

for dir in ${TTRSS_PATH}/*; do

INSTANCE_NAME=${dir##*/}

start-stop-daemon --stop --make-pidfile --quiet

--retry=TERM/1/KILL/5

--pidfile "${TTRSS_PIDDIR}/ttrss-${INSTANCE_NAME}.pid"

RETVAL="$?"

[ "$RETVAL" = 2 ] && return 2

start-stop-daemon --stop --quiet --oknodo --retry=0/1/KILL/5

--exec ${DAEMON}

[ "$?" = 2 ] && return 2

rm -f "${TTRSS_PIDDIR}/ttrss-${INSTANCE_NAME}.pid"

return $RETVAL

done

}

case "$1" in

start)

log_daemon_msg "Starting $DESC" "$NAME"

do_start

case "$?" in

0|1) log_end_msg 0 ;;

2) log_end_msg 1 ;;

esac

;;

stop)

log_daemon_msg "Stopping $DESC" "$NAME"

do_stop

case "$?" in

0|1) log_end_msg 0 ;;

2) log_end_msg 1 ;;

esac

;;

restart|force-reload)

# If the "reload" option is implemented then remove the

# 'force-reload' alias

log_daemon_msg "Restarting $DESC" "$NAME"

do_stop

case "$?" in

0|1)

do_start

case "$?" in

0) log_end_msg 0 ;;

1) log_end_msg 1 ;; # Old process is still running

*) log_end_msg 1 ;; # Failed to start

esac

;;

# Failed to stop

log_end_msg 1

;;

esac

;;

echo "Usage: ${NAME} {start|stop|restart|force-reload}" >&2

exit 3

;;

esac

# Set DISABLED to 1 to prevent the daemon from starting.
DISABLED=0

TTRSS_USERID="www-data"
TTRSS_GROUPID="www-data"
TTRSS_PIDDIR="/var/run"
TTRSS_PATH="/var/www/rss.heimdaheim.de/www"

# Allow the update_daemon script to use a forking daemon instead of a
# single-threaded instance.
# This option is only available for TinyTinyRSS 1.2.20 and above.
FORKING=0

# Set DISABLED to 1 to prevent the daemon from starting.

DISABLED=0

TTRSS_USERID="www-data"

TTRSS_GROUPID="www-data"

TTRSS_PIDDIR="/var/run"

TTRSS_PATH="/var/www/rss.heimdaheim.de/www"

# Allow the update_daemon script to use a forking daemon instead of a

# single-threaded instance.

# This option is only available for TinyTinyRSS 1.2.20 and above.

FORKING=0

Debian: dmesg output contains “Error: Driver ‘pcspkr’ is already registered, aborting…”

June 18, 2013June 18, 2013 Christian 1 Comment

Well, I recently prepared a bunch of Debian KVM guests, and today I got annoyed (basically because logwatch complains about it …) by this pesky error message on each startup. What causes this is error is really simple.

Udev loads the PC speaker driver (pcspkr) and then (for whatever reason) tries to load the alsa-module for the PC speaker (snd_pcsp). And the second one, basically fails. All we need to do, is create a blacklist.conf and add the latter one to it.

echo blacklist snd_pcsp | sudo tee -a /etc/modprobe.d/blacklist.conf

1	echo blacklist snd_pcsp \| sudo tee -a /etc/modprobe.d/blacklist.conf

open-vm-tools for Debian Etch

March 27, 2008June 21, 2013 Christian 2 Comments

Well, after a loooong time of trying to get the modules and all the other stuff (read: init-script for the guest daemon and modules) working, I think I’m about there.

I finally fixed a long-standing issue, with the postinst/prerm scripts, and the tools should be about ready. Gonna try and send it Daniel Baumann’s way (that is the Debian Maintainer), for proper inclusion into Lenny.

I (successfully) tried splitting the Xorg parts from the “normal” open-vm-tools, as I usually don’t want Xorg installed on *any* of my virtual machines. Thus leaving me with open-vm-tools, open-vm-modules and open-vm-toolbox (and open-vm-source) as a list of packages one could install.

Nagios & plugins

October 6, 2007August 16, 2014 Christian Leave a comment

Since we started utilizing Nagios‘s power two months ago, I finally came up with a C-based ram-plugin for nagios. The biggest problem I had with the python and perl based plugins, that some distributions (yes, SLES and Debian) don’t install either Python or Perl.

Since I wanted a manageable setup (as in unified code base across all distributions), I wanted it to work without installing too much. So I took the swap plugin and basically removed what wasn’t necessary and voila!

Here we go, yay ME!

Only thing I need to finish sometime soon, is getting the NSClient++ work on my Windows boxen (which I do have quite a few, the domain controllers, nas-cluster, …)

Being oblivious

September 8, 2007September 8, 2007 Christian Leave a comment

Well, the title nearly says everything .. I managed to loose my second pair of car keys, today I somehow found out that I was driving without a drivers license, so I have to go to the registration office and apply for a new one, hopefully should be done in about 4-6 weeks. Oh hell, and I have to spend about 40 € on it ..

Well, live kinda sucks if you’re oblivious. Anyway, work is giving me a ass-load of fun right now, so I’m kinda happy, though it’s Saturday evening, I’m sitting back home, just lost all my custom build Debian packages (yes, I happen to use that at work, right after SLES) and listening to Hed PE.