The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

    Mastodon

  • Twitter Updates

  • My Flickr Stream

    20140508-Delphi-2007--Project-Options--Cannot-Edit-Application-Title-HelpFile-Icon-Theming20140430-Fiddler-Filter-Actions-Button-Run-Filterset-now20140424-VMware-Fusion-6.0.3.-no-reclaimable
    More Photos

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,862 other subscribers

Archive for the ‘*nix’ Category

« Previous Entries
Next Entries »

User Manual for Avira AntiVir Server | Unix and Avira AntiVir Professional | Unix

Posted by jpluimers on 2013/08/26

PDF User Manual for Avira AntiVir Server  | Unix and  Avira AntiVir Professional  | Unix.

It is not completely up to date (as most installations are now RPM based), but gives great background information.

If you are using SUSE Linux, then note that as of openSUSE 11.3, there is a glitch when you use the SUSE security repository (see Bug 633771 – antivir cannot be installed because of missing libdazuko.so).

Basically there are two solutions to this:

  1. Ignore the dependency issue;
  2. Use the Avira repository.

The former seems to be a viable solution as per PDF User Manual, the installation proceeds as follows:

linking /usr/lib/AntiVir/guard/libdazuko.so to /usr/lib/AntiVir/guard/
libdazuko3compat2.so...

And indeed it does: these are the steps to follow, first for adding the security repository, then to install the package (click on images to view larger versions): Read the rest of this entry »

Posted in *nix, Linux, openSuSE, Power User, SuSE Linux | Leave a Comment »

Installing SuSE 11.2 or higher: before the first reboot the CLI version of YaST looks horrible. Reboot or second CLI fixes it.

Posted by jpluimers on 2013/08/19

Since SuSE 11.2, when installing then the CLI version of YaST looks horrible on the first (Ctrl-Alt-F1) console before you do your first reboot.

Workarounds:

  1. Try one of the other consoles,
  2. Reboot once.

It still fails at SuSE 12.x.

Before/After (click on the images to enlarge):

YaST before reboot

YaST before reboot

YaST after reboot

YaST after reboot

–jeroen

Posted in *nix, Linux, openSuSE, Power User, SuSE Linux | Leave a Comment »

Getting a fresh root hint file on SUSE 12.x

Posted by jpluimers on 2013/07/31

Wrote a small script that goes into my monthly crontab.

It gets ftp://ftp.internic.net/domain/named.cache into /var/lib/named/named.cache.new, and logs when you need to copy it over into /var/lib/named/root.hint

Read the rest of this entry »

Posted in *nix, Development, Linux, Power User, Scripting, Sh Shell, Software Development, SuSE Linux, wget | Leave a Comment »

Dilbert RSS alternative/workaround (via: Kimmo Suominen)

Posted by jpluimers on 2013/07/08

Since about 2 weeks, the official Dilbert RSS feed stopped providing Dibert comic images asking you to

“Dilbert readers – Please visit Dilbert.com to read this feature. Due to changes with our feeds, we are now making this RSS feed a link to Dilbert.com.”

Luckily, Kimmo Suominen has provided a new RSS feed that does which I found through workaround new dilbert rss

In fact he created two, as his historical one (http://kimmo.suominen.com/stuff/dilbert.xml) used to have a redirect to the official one which somehow got permanently picked up by Feedly (don’t you love redirection technology) thereby not picking up the second change to the feed.

This is the new feed that works all the time:

http://kimmo.suominen.com/stuff/dilbert-daily.xml

Which reminds me: if it is on the net, you cannot hide it, or prevent others from accessing it.

–jeroen

via: Dilbert RSS – Kimmo Suominen.

Posted in *nix, Power User | Leave a Comment »

a few notes on sendmail and re-trying deferred messages

Posted by jpluimers on 2013/07/05

My sendmail setup is a 2-staged one.
Every once in a while one of the stages stops, and mostly they recover.
Sometimes the second stage doesn’t, which causes a lot of messages in the queue get the deferred status.

Re-trying those deferred messages was a bit of a trial and error case, as my search efforts resulted in a lot of messages telling me what should work, but not what actually works.

First of all, mailq shows you what is stuck in the queue.

snap:~ # mailq
                /var/spool/mqueue (2 requests)
-----Q-ID----- --Size-- -----Q-Time----- ------------Sender/Recipient-----------
q9FLFBkD002197    11967 Mon Oct 15 23:15 MAILER-DAEMON
                 (Deferred: Connection timed out with smtp.anbid.com.br.)
                                         <debutvtr1@anbid.com.br>
q7S6oxgS023145     5067 Tue Aug 28 08:50 MAILER-DAEMON
      8BITMIME   (Deferred: Connection timed out with mail.admail.com.ar.)
                                         <trustiest76@admail.com.ar>
                Total requests: 2

You can add some parameters for it to show other queues.

So I have a little mq script that shows all queues:

#!/bin/bash
echo "Outgoing mailq";
sudo mailq;
echo " ";
echo "Submit mailq";
sudo mailq -Ac;
echo " ";
echo "Incoming mailq";
sudo mailq -C/etc/sendmail-rx.cf;

These are the commands I tried to flush the outgoing mailq:

sendmail -v -q
sendmail -v -q -OTimeout.hoststatus=0m
sendmail -v -qR@

Only the last one worked correctly.

–jeroen

Posted in *nix, Linux, Power User | Leave a Comment »

If you by accident press Ctrl-Z on the Linux console, use fg to un-suspend that task

Posted by jpluimers on 2013/07/01

The Linux console has different shortcut keys than many people are used to, so Ctrl-Z is not “undo”, but “suspend”. It sends and returns you to the command prompt.

The easiest way to undo that is to type fg, which brings back the suspended process into the foreground.

A nice post with a bit more background information is Bg, Fg, &, Ctrl-Z – 5 Examples to Manage Unix Background Jobs.

–jeroen

via: What is effect of CTRL + Z on a unix\Linux application – Super User.

Posted in *nix, Linux, Power User | Leave a Comment »

mutt notes

Posted by jpluimers on 2013/06/28

When the webmail doesn’t do what I want, I fall back on mutt on the Linux command line prompt.

It is an immensely strong and stable text based mail client, but – beyond the basics – has a steep learning curve.

In fact it is so stable, that the CVS repository rarely gets commits

So below a few notes that I used to clean up truckloads of mail.

  1. Read Real Programmers: Jump Start: Mutt — by hackers, for hackers. It is a very short introduction with the most powerful.
  2. Read My first mutt : Searching mail (the best article on My first mutt), and My first mutt : mutt overview. They why limit is far more useful than search, and the basic UI concept of mutt.
  3. The mutt documentation has a text based man page.
  4. But there is both a html manual and text manual
    (the devel doc branch has both html manual and text manual too).
  5. A lot of actions in mutt depends on patterns which are based on regular expressions.

For me the most powerful combination of steps is this:

  1. Limit the message view to a search pattern of messages you are looking for
  2. Tag the (groups of) messages you want to operate on
  3. Use the semicolon tag-prefix command to operate only on the tagged messages [Wayback/Archive] Mutt: apply command to all tagged messages – Super User
    Once you have tagged the desired messages, you can use the tag-prefix operator, which is the ; (semicolon) key by default. When the tag-prefix operator is used, the next operation will be applied to all tagged messages if that operation can be used in that manner.

A few more details are below. Read the rest of this entry »

Posted in *nix, Cygwin, Linux, Power User | 1 Comment »

Reminder to self: 3 months ago “all mine!: openSUSE 12.3 is out!”

Posted by jpluimers on 2013/06/13

Time to try out the 3 months old release and see how much got fixed in the mean time.

–jeroen

via: all mine!: openSUSE 12.3 is out!.

Posted in *nix, Linux, openSuSE, Power User, SuSE Linux | Leave a Comment »

ASUS RT N66U did not update DDNS with changed IP addres

Posted by jpluimers on 2013/06/11

Today my router had an IP-address change, but didn’t update the DynDNS.org information in my My Host Services | My Dyn Account. Which meant I could not “phone home”, as I didn’t know the new IP-address**.

Lesson re-learned:

During initial router configuration, watch the router logs, as you might have accidentally updated the DynDNS.org by hand, not by your router

Had this in the ASUS Wireless Router RT-N66U – General Log:

Jun 11 08:01:53 notify_rc : restart_ddns
Jun 11 08:01:53 ddns: clear ddns cache file for server setting change
Jun 11 08:01:53 ddns update: connected to members.dyndns.org (204.13.248.111) on port 80.
Jun 11 08:01:53 ddns update: server output: HTTP/1.1 200 OK^M Date: Tue, 11 Jun 2013 06:01:53 GMT^M Server: Apache^M X-UpdateCode: X^M Content-Length: 7^M Connection: close^M ^M notfqdn
Jun 11 08:01:53 ddns update: malformed hostname: myhostname

The problem: hostname should not only be the name of the host, but the FQDN of the host. Read the rest of this entry »

Posted in ASUS RT-N66U, Network-and-equipment, openSuSE, Power User, SuSE Linux | Tagged: , , , , | 2 Comments »

Relevant files for ssh-keygen – Wikipedia, the free encyclopedia

Posted by jpluimers on 2013/05/13

Edit:

After writing this, DSA got deprecated then later removed. See [WayBack] Secure Secure Shell.

When working with SSH private/public keys (often because of ssh-keygen), and using DSA for auhtentication, these are the relevant files:

  • $HOME/.ssh/id_dsa:
    (on the local system)
    The $HOME/.ssh/id_dsa file contains the protocol version 2 DSA authentication identity of the user.
  • $HOME/.ssh/id_dsa.pub:
    (on the local system)
    The $HOME/.ssh/id_dsa.pub file contains the DSA public key for authentication when you are using the SSH protocol version 2. A user should copy its contents in the $HOME/.ssh/authorized_keys file of the remote system where a user wants to log in using DSA authentication.
  • $HOME/.ssh/authorized_keys:
    (on the remote system)
    The $HOME/.ssh/authorized_keys file contains authorized DSA public keys (each line is the contents of a $HOME/.ssh/id_dsa.pub file) of users on systems that are auhorized to login on the remote system.

Important:

Be sure to transfer the contents of the local $HOME/.ssh/id_dsa.pub file to the remote system in a secure way.

–jeroen

via ssh-keygen – Wikipedia, the free encyclopedia.

Posted in *nix, Apple, Cygwin, Endian, Linux, Mac, Mac OS X / OS X / MacOS, Mac OS X 10.4 Tiger, Mac OS X 10.5 Leopard, Mac OS X 10.6 Snow Leopard, Mac OS X 10.7 Lion, OS X 10.8 Mountain Lion, Power User | Leave a Comment »

« Previous Entries
Next Entries »