Bandwith limiting for Apache 2 (+ bw_mod 64bit RPM)
Thursday, February 23rd, 2006Sorry, there is no english version of this text for the moment, please select “Spanish” on the right menu bar if you can read it, and still wish to.
SuSE is one of the main linux distributions. I’ve been running it since version 6.0 and I can say that’s it’s the best one I’ve ever used (having tried Fedora at my job, and debian a long time ago).
Here I’ll post stuff related to this distro: tips, tricks, how to solve some problems, as well as RPMs packaged for my architecture (x86_64) among any other related things.
Sorry, there is no english version of this text for the moment, please select “Spanish” on the right menu bar if you can read it, and still wish to.
Sorry, there is no english version of this text for the moment, please select “Spanish” on the right menu bar if you can read it, and still wish to.
There are two ways of programming the time that cron jobs are run on SuSE Linux systems. One is adding entries to the user’s crontab using crontab -e, the other adding scripts (be it linked or copied) to the directories /etc/cron.hourly, /etc/cron.daily, /etc/cron.weekly and /etc/cron.monthly.
But the time, using the second method, is not configured the usual way: we see in /etc/crontab that every 15 minutes /usr/lib/cron/run-crons is run, a script which compares the timestamps of certain files with the current time in order to decide which cron jobs are to be run. These files are located at /var/spool/cron/lastrun and, quite expectedly, are named cron.hourly, cron.daily, etc.
So, if we want the daily jobs to be run at 6:00 AM, we must touch those files:
touch -t 200601240600 /var/spool/cron/lastrun/cron.daily
And that’s all. I don’t know when crontab usage was deprecated for daily, weekly, etc. task programming in SuSE, but it seems it was long ago.
More stuff from the past… I am now copying a little howto I wrote a long time ago as an introductory guide to RPM creation. It’s several years old, but I guess it’s still valid.
Bazaar is one of several implementations of the GNU-Arch version control system (the other one being TLA), and the one we use at my job due to its simpler interface and improved usability.
Here I make available a 64bit RPM of Bazaar 1.4, with a little patch of mine which makes the environment variable ARCH_LOG available to the hook upon commit.
As usual, the package is signed with my public GnuPG key.
Here is a brief description of what I had to do to migrate my running SusE 9.2 filesystem to a RAID1 made of my current hard drive and a new (identical) one.
Yesterday night I updated to KDE 3.4 and, as usual, I got a weird error
Authorization failed, An error occured during authentication: SASL(-4): no mechanism available: No worthy mechs found authentication not supported
Appart from the error string being built wrong, something which is more clearly seen on the spanish version of it (strings are mixed), this looks like that some plugin is missing. Kmail uses SASL as an authenthication abstraction layer, and each protocol supported by SASL is built as a plugin and packaged in its own RPM, or at least that’s what SuSE does.
As you might know, DVD support in SuSE is crippled due to legal restrictions. In addition to not distributing a binary capable of encrypted DVD playback, they are not distributing the source code to xine-lib, most probably because of legal concerns as well.
Luckily enough, they do distribute de RPM .spec file they use to build the package, and it is ready to build all the plugins, even the “forbidden” ones. Using it to obtain a fully functional xine-lib for your AMD64 in a nice SuSE aware RPM is quite straightforward. You can either follow the instructions here, or forget about it and download the packages I prepared.
Doesn’t Amarok’s cover fetcher work on the latest SuSE’s 9.2 build? Here I’m talking about Amarok 1.2beta3, the audio player for KDE.
Having wondered for a while what was wrong, and just in case somebody happens to experience this very same problem, I’ll say here for the record that there is no bug (at least here).
Simply choose a locale setting inside Amarok’s Cover Manager (you’ll find a drop down list at the top of the window) and everything will work.
Anyone should work, but if you find that some of your covers were not fetched, you can try on a different locale (i.e. server). I got lots of covers from the german server which were not on the british one.
By the way, lots of covers are not well matched. And I mean lots. It’s funny (or rather disgusting) to see “Chill Out XXX” while listening to Brahms…