Re: [CentOS] Is there an sshguard script for logwatch?
> -Original Message- > From: Always Learning > Sent: Thursday, November 21, 2019 4:25 PM > > On Thu, 2019-11-21 at 13:44 +0100, Adrian van Bloois wrote: > > > I wonder if there is a script to analyze logfiles for llogwatch and > > sshguard? > > Anyone knows? > > You can take an existing script, for another piece of software reported > by Logwatch, retain the beginning and ending parts, and create your own > version. The completed script should be placed in /etc to ensure it is > not over-written by software updates. A supplemental RPM will help you with this ... > > It can be difficult sorting-out the names of the different scripts and > their directory locations, but I did it despite being unfamiliar with > the programming language - Python ? There is a logwatch mailing list, I am on it... If you need help authoring it, post there. Logwatch-devel on lists.sourceforge.net > > I did it in C5 and C6 for Exim some years ago and the result was ideal > for my requirements. > v/r, Jason Pyeron ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Is there an sshguard script for logwatch?
On Thu, 2019-11-21 at 13:44 +0100, Adrian van Bloois wrote: > I wonder if there is a script to analyze logfiles for llogwatch and > sshguard? > Anyone knows? You can take an existing script, for another piece of software reported by Logwatch, retain the beginning and ending parts, and create your own version. The completed script should be placed in /etc to ensure it is not over-written by software updates. It can be difficult sorting-out the names of the different scripts and their directory locations, but I did it despite being unfamiliar with the programming language - Python ? I did it in C5 and C6 for Exim some years ago and the result was ideal for my requirements. Happy Christmas to everyone. Paul. England belongs in the EU ... and no Donald ! England is NOT for sale! ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Issue with "ExecStartPost" attribute in systemd daemon faile
Gestió Servidors wrote: Hello, I'm trying to configure a daemon (I'm doing tests with "crond" daemon) to send me an email after daemon restart. My "crond.service" file is: # /etc/systemd/system/crond.service [Unit] Description=Command Scheduler After=auditd.service systemd-user-sessions.service time-sync.target #OnFailure=crond-notify-email@%i.service [Service] EnvironmentFile=/etc/sysconfig/crond ExecStart=/usr/sbin/crond -n $CRONDARGS ExecReload=/bin/kill -HUP $MAINPID KillMode=process Restart=on-failure RestartSec=10s ExecStartPost=/bin/sh -c "/etc/systemd/system/test.sh" [Install] WantedBy=multi-user.target My "test.sh" is very simple: #!/bin/sh echo "CROND is restarting" | /usr/bin/mailx -s "crond failure notification" myemailaddress@mydomain As you can see, I have added lines "Restart=on-failure", "RestartSec=10s" and " ExecStartPost=/bin/sh -c "/etc/systemd/system/test.sh"" to the original crond.service daemon file. Then, I run "systemctl daemon-reconfigure" and, from one console, I run "kill -9 `pidof cron`" for restarting crond daemon. After it, I receive an email... But now, if I run again ""kill -9 `pidof cron`", I don't receive any mail... I have notice that if I run "systemctl daemon-reload" and then kill crond process, mail is sent perfectly... but if I don't run "systemctl daemon-reload", mail is sent ONLY first time... Why? I guess it is probably the way systemd works - subsequent 'crashes' (or kills in you case) probably only restart the main process (ExecStart) and don't re-run the ExecStartPost bits ... I notice you have a commented out an 'OnFailure' line in the unit file - so I guess you've been experimenting with that - which I believe is actually the way to do what you need ? James Pearson ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS-announce] CEBA-2019:3856 CentOS 6 udev BugFix Update
CentOS Errata and Bugfix Advisory 2019:3856
Upstream details at : https://access.redhat.com/errata/RHBA-2019:3856
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
e238940087eba7a77b8e80ddc062fb8b27d1c2154e7216c14615c62a11bb1171
libgudev1-147-2.74.el6_10.i686.rpm
fe383c264f0d1d887fbc3103bc78a9d379b7bdf0e54830d2be489b94ad969c42
libgudev1-devel-147-2.74.el6_10.i686.rpm
109fb20d3900b3997b0a5e9ffbdc0d6dfe2cc612921b81f58c50a9029f7fa9d9
libudev-147-2.74.el6_10.i686.rpm
763903775dc41c7e615ac6b81475c86a7fc021d7374d19fccbbb25af1d9c38b7
libudev-devel-147-2.74.el6_10.i686.rpm
e6dc596d6e4b71fec1d61a1b97d79c980213c2bb181856b9c502808b32511deb
udev-147-2.74.el6_10.i686.rpm
x86_64:
e238940087eba7a77b8e80ddc062fb8b27d1c2154e7216c14615c62a11bb1171
libgudev1-147-2.74.el6_10.i686.rpm
a2084d7196fc5fadb1ade692409247fef882c86dda0fc019c6bd258d53493793
libgudev1-147-2.74.el6_10.x86_64.rpm
fe383c264f0d1d887fbc3103bc78a9d379b7bdf0e54830d2be489b94ad969c42
libgudev1-devel-147-2.74.el6_10.i686.rpm
ad3e6b2c8fc162981001985a3109cf11e4e61978bedc995a4425608cf5b6fdf9
libgudev1-devel-147-2.74.el6_10.x86_64.rpm
109fb20d3900b3997b0a5e9ffbdc0d6dfe2cc612921b81f58c50a9029f7fa9d9
libudev-147-2.74.el6_10.i686.rpm
d2a3a49abcaf44923af02a46b3a33dd79325365f8560d7a570609b96286cdb4e
libudev-147-2.74.el6_10.x86_64.rpm
763903775dc41c7e615ac6b81475c86a7fc021d7374d19fccbbb25af1d9c38b7
libudev-devel-147-2.74.el6_10.i686.rpm
4bbf43f5a02ec59527c1fd8909fb7f85ff5c47a9bb38bf81f3fbbc6ec282481b
libudev-devel-147-2.74.el6_10.x86_64.rpm
226ab4ca0abe61cfe9b7b91ae9185087f39ddc4338aea7b22bf0f54717f5da31
udev-147-2.74.el6_10.x86_64.rpm
Source:
43ceefd949dc838ce1fc222bb4e8b00f7198e4433277a6ac2e574479517e3ee2
udev-147-2.74.el6_10.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS
___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce
Re: [CentOS] can't login as subsequent FreeIPA users
Carson Chittom writes: > When I set up a machine with CentOS 8, I used the "Enterprise Login" in > the initial setup wizard to authenticate against my FreeIPA server. > This worked fine, and I have no issues logging in with that initial user. > > However, I am unable to use GDM or the console to login as any *other* > valid user from FreeIPA. From GDM I get something like "Sorry, that > didn't work" and "Permission denied" on the console. I've verified that > the credentials are correct, and that I am able to manually get a ticket > via kinit for one of those other users from this machine. With > CentOS 7, I didn't have to do any additional configuration in this > regard after the initial wizard. I discovered that /etc/sssd/sssd.conf contains the line: simple_allow_users = $, initialuser Adding other users to this line allows them to log in. This is a very small deployment (8 users, 4 machines), so this addresses my immediate need, but clearly isn't really the solution. I'll dig into it some more when I have some leisure. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Issue with "ExecStartPost" attribute in systemd daemon faile
Am 21.11.19 um 14:28 schrieb Gestió Servidors: Hello, I'm trying to configure a daemon (I'm doing tests with "crond" daemon) to send me an email after daemon restart. My "crond.service" file is: # /etc/systemd/system/crond.service [Unit] Description=Command Scheduler After=auditd.service systemd-user-sessions.service time-sync.target #OnFailure=crond-notify-email@%i.service [Service] EnvironmentFile=/etc/sysconfig/crond ExecStart=/usr/sbin/crond -n $CRONDARGS ExecReload=/bin/kill -HUP $MAINPID KillMode=process Restart=on-failure RestartSec=10s ExecStartPost=/bin/sh -c "/etc/systemd/system/test.sh" [Install] WantedBy=multi-user.target My "test.sh" is very simple: #!/bin/sh echo "CROND is restarting" | /usr/bin/mailx -s "crond failure notification" myemailaddress@mydomain As you can see, I have added lines "Restart=on-failure", "RestartSec=10s" and " ExecStartPost=/bin/sh -c "/etc/systemd/system/test.sh"" to the original crond.service daemon file. Then, I run "systemctl daemon-reconfigure" and, from one console, I run "kill -9 `pidof cron`" for restarting crond daemon. After it, I receive an email... But now, if I run again ""kill -9 `pidof cron`", I don't receive any mail... I have notice that if I run "systemctl daemon-reload" and then kill crond process, mail is sent perfectly... but if I don't run "systemctl daemon-reload", mail is sent ONLY first time... Why? What is "status" showing (systemctl status crond)? For both cases (first/second kill)? Any differences? -- Leon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Issue with "ExecStartPost" attribute in systemd daemon faile
Hello, I'm trying to configure a daemon (I'm doing tests with "crond" daemon) to send me an email after daemon restart. My "crond.service" file is: # /etc/systemd/system/crond.service [Unit] Description=Command Scheduler After=auditd.service systemd-user-sessions.service time-sync.target #OnFailure=crond-notify-email@%i.service [Service] EnvironmentFile=/etc/sysconfig/crond ExecStart=/usr/sbin/crond -n $CRONDARGS ExecReload=/bin/kill -HUP $MAINPID KillMode=process Restart=on-failure RestartSec=10s ExecStartPost=/bin/sh -c "/etc/systemd/system/test.sh" [Install] WantedBy=multi-user.target My "test.sh" is very simple: #!/bin/sh echo "CROND is restarting" | /usr/bin/mailx -s "crond failure notification" myemailaddress@mydomain As you can see, I have added lines "Restart=on-failure", "RestartSec=10s" and " ExecStartPost=/bin/sh -c "/etc/systemd/system/test.sh"" to the original crond.service daemon file. Then, I run "systemctl daemon-reconfigure" and, from one console, I run "kill -9 `pidof cron`" for restarting crond daemon. After it, I receive an email... But now, if I run again ""kill -9 `pidof cron`", I don't receive any mail... I have notice that if I run "systemctl daemon-reload" and then kill crond process, mail is sent perfectly... but if I don't run "systemctl daemon-reload", mail is sent ONLY first time... Why? Thanks. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Is there an sshguard script for logwatch?
Hi all, I wonder if there is a script to analyze logfiles for llogwatch and sshguard? Anyone knows? Adrian -- Adri P. van Bloois "Elegance is not a dispensable luxury but a factor that decides between success and failure." Edsger W. Dijkstra ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
