Despite I’d really like to keep this blog lively and updated, time is working against me… so I end up doing pretty much nothing here.
To connect with me or check out more frequent updates refer to one of my social profiles on:
Have been banging my head on this for a while now. Logwatch kept reporting in his daily summary something along the lines of what below:
——————— clam-update Begin ————————
No updates detected in the log for the freshclam daemon (the
ClamAV update process). If the freshclam daemon is not running,
you may need to restart it. Other options:
A. If you no longer wish to run freshclam, deleting the log file
(default is freshclam.log) will suppress this error message.
B. If you use a different log file, update the appropriate
configuration file. For example:
echo “LogFile = log_file” >> /etc/logwatch/conf/logfiles/clam-update.conf
where log_file is the filename of the freshclam log file.
C. If you are logging using syslog, you need to indicate that your
log file uses the syslog format. For example:
echo “*OnlyService = freshclam” >> /etc/logwatch/conf/logfiles/clam-update.conf
echo “*RemoveHeaders” >> /etc/logwatch/conf/logfiles/clam-update.conf
———————- clam-update End ————————-
suggesting that either clam-update was not running or the log file location was misconfigured.
Checked all that a number of times, made sure the permissions were correct, no difference.
Finally I realized that there is an error in the date detection of the freshclam related script which comes with Logwatch 7.3.6, and the solution comes down to editing the file:
and at around line 89 (this on CentOS 6.5) replace:
$ThisLine =~ s/ $//;
$ThisLine = substr($ThisLine, 28);
Craving for a sweet, soft, chilly, low carbs & low calories dessert? Then this approach I perfected after a few tryouts might just be what you’re looking for, especially if you only have an handful of minutes to spare.
– Fat free milk: 50 ml of fat free milk
– Fat free yogurt: 7 to 9 teaspoonfuls
– Sugar substitute at taste
The yogurt can be either plain or flavored, and if you don’t mind a few extra calories low fat or whole milk and sugar in place of the fat-free choices above will work just fine.
They say a picture is worth a thousand words, while a video is worth… not sure how many words. At any rate, here you go with the video whose lenght (a little over two minutes) is exactly the time it takes to get the mousse ready:
Tools and Tips
– Glass cup: this should be cone-like shaped, which appears helping the frother to produce as much milk foam as possible. Also, the cup should be placed in the freezer for at least 30 minutes before use. This will make the foam think and compact.
– Milk frother: my favorite is the Aerolatte, but cheaper alternatives (such as the $3 model I’ve recently spotted at Ikea) produce pretty good results as sell.
– Place the mousse in the freezer for 30 – 45 minutes for best results.
And now, on a side-note, for who wonders whether it should be “yogurt” or “yoghurt”, turns out both terms appear to be acceptable.
Here are the steps necessary in order to have the SFTP subsystem of the SSH (secure shell) daemon log operations on disk.
1. edit /etc/ssh/sshd_confing and look for the line:
#Subsystem sftp /usr/libexec/openssh/sftp-server
Uncomment it and update it as follows:
Subsystem sftp /usr/libexec/openssh/sftp-server -l INFO -f LOCAL6
-l INFO instructs the sftp server subsystem of the sshd daemon to log events, while -f LOCAL6 tells it to use the corresponding facility code
2. edit /etc/rsyslog.conf and add the following rule:
# Save sftp-server mesages to sftp.log local6.* /var/log/sftp.log
3. restart the sshd and the rsyslog demons (/etc/init.d/sshd restart and /etc/init.d/rsyslogd restart — specific command might vary based on your Linux distro, and of course you need to be root or use “su” in order to issue them)
Moving forward sftp actions will be logged in /var/log/sftp.log
For specifics on the sftp server log options and type of messages logged see the related man page.
I recently started getting into nodejs, and first thing to figure out has been the best way to install it on a CentOS virtual server I had around, and here’s a summary of my findings.
In order to install nodejs on RedHat / CentOS / Fedora the most common approach is to grab the latest sources tarball and build them, and the instructions for this are on the online wiki. This will install node.js as an unmanaged package, making upgrade or uninstallation at times not super straightforward.
Which is why, on RedHat based distros (such as CentOS) I prefer going for handling software installations through RPM. In the past there were some ready-made node.js RPMs, but no new ones have been produced after version 0.6.18 (and we are now at 0.8.x).
So I went for building the RPMs myself, and listed below are the steps I went through.
– If your CentOS box doesn’t have compiler related components, install them with yum as usual:
yum groupinstall “Development tools”
– Install also the gcc-c++ build tools (needed by the RPM build environment)
yum install gcc-c++
– Setup the RPM build environment, following what outlined on the CentOS wiki — afterward your home user’s folder show include the following subfolders:
– Download the latest node.js sources in the SOURCES folder
curl -sR -o ~/rpmbuild/SOURCES/node-v0.8.14.tar.gz http://nodejs.org/dist/v0.8.14/node-v0.8.14.tar.gz
– In order to build an RPM you’ll need its definition (.spec) file, and someone out there is kind enough to maintain one up to date with the latest node.js versions. Download it in the SPECS folder:
curl -sR -o ~/rpmbuild/SPECS/node-v0.8.14.spec https://github.com/kazuhisya/nodejs-rpm/raw/master/nodejs.spec
– At this point you’re ready to fire up rpmbuild:
rpmbuild -ba ~/rpmbuild/SPECS/node-v0.8.14.spec
– Depending on how fast your machine is, after a few minutes unless surprises the build and packaging process will complete and under ~/rpmbuild/RPMS/<architecture> you’ll find the node.js binaries and source RPMs.
– In my case, being the CentOS box a 64 bit one, I found what was looking for at: ~/rpmbuild/RPMS/x86_64/nodejs-0.8.14-1.el6.x86_64.rpm
– At last, time to install node.js:
rpm -ivh ~/rpmbuild/RPMS/x86_64/nodejs-0.8.14-1.el6.x86_64.rpm
– once installed, you can verify if things went correctly by checking that the “node” executable can be found within the path (doing a “which node”) and node –version which should output the version of the node binary just installed.
If you wish to cut a few corners and avoid the steps above, you can find the node.js 0.8.14 RPMs at this location (note that they have been built on an x64 CentOS 6.3 box — haven’t tried them on other versions or distros).
Sign up to receive email updates and to hear what's going on with me!