Faillog in Fedora

First of all, this is just my own experience from an Red Hat magazine named How do I use the faillog program to track failed login attempts?

Let’s go:

  1. Open the /etc/pam.d/system-auth file for editing.
  2. Add the following lines:

    auth required no_magic_root
    account required deny=2 no_magic_root
  3. Save the file and exit.
  4. Test the configuration by attempting to login as a root, but using a wrong password.
  5. Here’re my 5 cents: type this: (my output appears in spanish)
    [root@soseck ~]$ faillog -u root
    User Fails Máx Last Active
    root 1 0 03/01/07 07:40:02 +0100 pts/0
  6. Keep in mind that if your’re using the authconfig tool your changes at /etc/pam.d/system-auth will be lossed next time authconfig runs.

More from my own: as a root you should use system-config-suthentication (by typing from a console, for instance) if you want to have a look on how yor system is configured. I recommend you have a look on faillog manual page. It comes with very useful parameters that makes me feel I ‘ll need a next post to talk about it, such a lock-time that lock an account during a number of seconds after a failed login.

Shrek 2 and Red Hat

I’ve been looking over Red Hat Magazine, I’ve found a non technical article about Geek movies that should be on you queue (by the way here we got something similar with Top 10:las mejores películas geek) and reading some comments -’cause I feel that there’re some importants absences, I’ve follow a link to Linux behind the magic of shrek 2 where it’s reported that Red Hat Linux was used as a main platform to develop the film.

Nice, but not new, happen to ILM where started with SGI but they move to Linux (I really don’t remenber which particular platform they choosed). If you need a sample on using Linux here you got once more.

How to join several pdf’s files in just one

Thanks to Pablo Iranzo for send me that line:
gs -q -sPAPERSIZE=a4 -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile=out.pdf $*

it is usefull to join several pdf’s files in just one.

Imagine you download the book Linux Kernel in a Nutshell (which is a good idea if you wanna learn things about Linux kernel ). That book is free offered in multiple pdf’s files, but you want to send it straight to the printer in just one step and without blank pages, you’d better got a single pdf file.

Graphical terminals clients in Gnome

As higher my Gnome version is, as slower it goes … well not really. Sometimes Gnome guys improve its behavior, not just add features

But as my RAM hasn’t grow up since I buy my laptop -I got 256 of RAM yet- I was looking how to obtain more performance… first thing I done was to switch from Gnome to XFCE and it really gives me an improvement but now I’m again with Gnome, don’t ask me why…

Now I’m looking how much memory my command line uses… here’re the data:

  1. gnome-terminal: 40.408 KB
  2. Terminal: 29.312
  3. xterm:10.824

Some other differences has to be keep in mind. Althoug xterm is really fast and light sometimes is too simple. I like tabs in my terminals, as far as I know there’re no tabs in xterm, you only get something similar by using screen, which is also light and fast but a little bit… hard.

Gnome-terminal is the best option, or so it seems until I discover Terminal from XFCE. As authors says at their page is an alternative to gnome-terminal -my choice on gnome- but saving all those weightly libraries from gnome, so the same but faster and lighter.

This days I’m getting familiar with Terminal, with means nothing ’cause I really need a very basic console use and this is exactly as gnome-terminal is.

Screen: mini, mini howto

As long as Santiago Romero tolds me screen was useful I know it must be true. Finally I’m testing it, here’re a few tips:

  • type screen to start up the program; nothing spectacular will happend
  • type Control+a+c to create a new terminal
  • type Control+a+p to go to previous terminal
  • type Control+a+n to go to next terminal

Finally, let’s assume that you’ve lost your connection -no matter why-, later, you log-in again, if you were using screen, jsut type: screen -D -R and voilà! you will recover your former session as it was.

If you read spanish it would help you this Tutorial de screen en español