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:scratch: |
vim /home/USER_NAME/.bashrc
Code:
grep -i failed /var/log/secure | tail -n 10 |
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, https://access.redhat.com/site/solutions/217423
Note: 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 http://www.rsyslog.com/doc/troubleshoot.html #### 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 #### GLOBAL DIRECTIVES #### # 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/ip:port, e.g. 192.168.0.1:514, port optional #*.* @@remote-host:514 # ### end of the forwarding rule ### Take care, John |
All times are GMT -5. The time now is 11:30 PM. |