Visit Jeremy's Blog.
Go Back > Forums > Linux Forums > Linux - Newbie
User Name
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!


  Search this Thread
Old 07-23-2013, 04:48 PM   #1
Registered: Jul 2010
Posts: 64

Rep: Reputation: 1
Unhappy RHEL 6 - Upon GUI Login Present successful and unsucessful User Login

I have a customer requirement that stipulates when users login to RHEL6 they be presented with there last successful login and in the case of a bad login, between successful logins, when (date/time) the bad login occured.

Does anyone have a script and if so where can I place this script in the users startup.

A million thanks,
Johnny Mac
Old 07-23-2013, 05:37 PM   #2
Senior Member
Registered: Aug 2006
Location: Detroit, MI
Distribution: GNU/Linux systemd
Posts: 4,211

Rep: Reputation: 1612Reputation: 1612Reputation: 1612Reputation: 1612Reputation: 1612Reputation: 1612Reputation: 1612Reputation: 1612Reputation: 1612Reputation: 1612Reputation: 1612
vim /home/USER_NAME/.bashrc

grep -i failed /var/log/secure | tail -n 10
1 members found this post helpful.
Old 07-24-2013, 01:38 PM   #3
Registered: Jul 2010
Posts: 64

Original Poster
Rep: Reputation: 1
The above only works as root and only in console (not graphical user interface). Solution was I modified the /etc/rsyslog.conf to write /var/log/secure messages to a second location. When users login they grep against the second file (users read only) for bad logins. The second request (succesful logins) I identifed the solution by going to Red Hat's website,

To get the application to startup upon user login, I used the graphical interface System - Preferences - Startup Application. Here under command I typed, gnome-terminal and then the path to my grep script along with the file name and extension.

Below is my rsyslog.conf (/etc/) and script:

script - grep -i failed /var/log/secures | tail -n 10

# rsyslog v5 configuration file

# For more information see /usr/share/doc/rsyslog-*/rsyslog_conf.html
# If you experience problems, see

#### MODULES ####

$ModLoad imuxsock # provides support for local system logging (e.g. via logger command)
$ModLoad imklog # provides kernel logging support (previously done by rklogd)
#$ModLoad immark # provides --MARK-- message capability

# Provides UDP syslog reception
#$ModLoad imudp
#$UDPServerRun 514

# Provides TCP syslog reception
#$ModLoad imtcp
#$InputTCPServerRun 514


# Use default timestamp format
$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat

# File syncing capability is disabled by default. This feature is usually not required,
# not useful and an extreme performance hit
#$ActionFileEnableSync on

# Include all config files in /etc/rsyslog.d/
$IncludeConfig /etc/rsyslog.d/*.conf

#### RULES ####

# Log all kernel messages to the console.
# Logging much else clutters up the screen.
#kern.* /dev/console

# Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
*.info;mail.none;authpriv.none;cron.none /var/log/messages

# The authpriv file has restricted access.
authpriv.* /var/log/secure

# The authpriv file has restricted access.
authpriv.* /var/log/secures

# Log all the mail messages in one place.
mail.* -/var/log/maillog

# Log cron stuff
cron.* /var/log/cron

# Everybody gets emergency messages
*.emerg *

# Save news errors of level crit and higher in a special file.
uucp,news.crit /var/log/spooler

# Save boot messages also to boot.log
local7.* /var/log/boot.log

# ### begin forwarding rule ###
# The statement between the begin ... end define a SINGLE forwarding
# rule. They belong together, do NOT split them. If you create multiple
# forwarding rules, duplicate the whole block!
# Remote Logging (we use TCP for reliable delivery)
# An on-disk queue is created for this action. If the remote host is
# down, messages are spooled to disk and sent when it is up again.
#$WorkDirectory /var/lib/rsyslog # where to place spool files
#$ActionQueueFileName fwdRule1 # unique name prefix for spool files
#$ActionQueueMaxDiskSpace 1g # 1gb space limit (use as much as possible)
#$ActionQueueSaveOnShutdown on # save messages to disk on shutdown
#$ActionQueueType LinkedList # run asynchronously
#$ActionResumeRetryCount -1 # infinite retries if host is down
# remote host is: name/iport, e.g., port optional
#*.* @@remote-host:514
# ### end of the forwarding rule ###

Take care,
1 members found this post helpful.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] How can I display a user's last login info, immediately after they login via gui? rgsurfs Linux - Newbie 3 05-17-2013 09:54 AM
Ubuntu/AD/KRB5/LDAP/NIS able to use domain user login with putty, unable in gui login Nitroglycerine Linux - Server 0 06-28-2012 05:17 AM
unable to login any user through the console but users can login in GUI p kumar Linux - Server 1 04-19-2012 07:09 AM
[SOLVED] Getting user's previous successful login before this one? arashi256 Linux - Newbie 7 08-24-2011 02:49 PM
Present a GUI Login on vnc connections PlatinumRik Linux - Software 1 04-18-2005 02:02 PM > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 02:50 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration