similar to: Issue with "ExecStartPost" attribute in systemd daemon faile

Hellos, Yes, I did some tests with "OnFailure" attribute, but the result was the same: system didn't sent any mail. Daemon and script files were: * crond.service: * [Unit] Description=Command Scheduler After=auditd.service systemd-user-sessions.service time-sync.target OnFailure=crond-notify-email.service [Service] EnvironmentFile=/etc/sysconfig/crond

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 >

Hi, it seems there is no difference in "systemctl status crond" :( El 22/11/2019 a las 13:00, centos-request at centos.org<mailto:centos-request at centos.org> escribi?: Message: 3 Date: Thu, 21 Nov 2019 14:41:25 +0100 From: Leon Fauster <leonfauster at googlemail.com><mailto:leonfauster at googlemail.com> To: centos at centos.org<mailto:centos at centos.org>

On 6 Apr 2020, at 12:21, Stephen John Smoogen wrote: > On Mon, 6 Apr 2020 at 04:16, Tobias Kirchhofer <collect at shift.agency> > wrote: > >> On 5 Apr 2020, at 21:20, Tobias Kirchhofer wrote: >> >>>>>> we experience difficulties with crond behaviour sending mail >>>>>> since >>>>>> CentOS 8.1. The cron job is the

I've been trying out the Restart= option in some of my own systemd service unit files - which appears to work fine However, I notice that this option is only used in a few OS provided service unit files - and was wondering about the wisdom of adding this capability to other daemons/services? (e.g. chronyd or ntpd, crond, rpcbind, etc, etc) - not that these daemons are likely to crash and

> On Mon, 6 Apr 2020 at 06:59, Tobias Kirchhofer <collect at shift.agency> > wrote: > >> On 6 Apr 2020, at 12:21, Stephen John Smoogen wrote: >> >> > On Mon, 6 Apr 2020 at 04:16, Tobias Kirchhofer <collect at shift.agency> >> > wrote: >> > >> >> On 5 Apr 2020, at 21:20, Tobias Kirchhofer wrote: >> >> >>

On Mon, 6 Apr 2020 at 06:59, Tobias Kirchhofer <collect at shift.agency> wrote: > On 6 Apr 2020, at 12:21, Stephen John Smoogen wrote: > > > On Mon, 6 Apr 2020 at 04:16, Tobias Kirchhofer <collect at shift.agency> > > wrote: > > > >> On 5 Apr 2020, at 21:20, Tobias Kirchhofer wrote: > >> > >>>>>> we experience difficulties

hi, is there somebody using systemd start script on fedora/centos7 + asterisk 13 in production? i have strange problem with high cpu usage when asterisk is started via systemd thanks for feedback p.s. systemd script is not in vanilla asterisk. only in fedora package info https://reviewboard.asterisk.org/r/2730/ -- --------------------------------------- Marek Cervenka

https://bugzilla.mindrot.org/show_bug.cgi?id=2512 Bug ID: 2512 Summary: Use IP_FREEBIND if available for sshd listening socket Product: Portable OpenSSH Version: 7.1p1 Hardware: Other OS: Linux Status: NEW Keywords: patch Severity: enhancement Priority: P5 Component: sshd

https://bugzilla.mindrot.org/show_bug.cgi?id=2512 Bug ID: 2512 Summary: Use IP_FREEBIND if available for sshd listening socket Product: Portable OpenSSH Version: 7.1p1 Hardware: Other OS: Linux Status: NEW Keywords: patch Severity: enhancement Priority: P5 Component: sshd

Hello All, I''m trying to capture the exception message that my server application is providing in response to my Ajax.Request. However, I''m confused as to when onFailure is fired vs. onException. The onException handler has access to the javascript exception object and I''d understood that it was only called when the dispatch fails. Not sure what exactly that means

Hi all, I have this code: new Ajax.Request(''non_existant.file'', { onSuccess:function(){alert("yay");}, onFailure:function(){alert("boo");} }); Why does the onFailure alert never get called? It works fine if I use a real file (onSuccess gets called). Thanks, Douglas

Hi All, I''m a super newbie with Prototype and am trying to implement my first solution using it. This is my code: var span = ''totalViews'' + video_id; var params = ''video_id='' + video_id; Ajax.Response(''trackVideo.php'', { method: ''post'', parameters: params, onSuccess: function(transport) {

Hello together. I''ve tried to register an onFailure behavior for all my Ajax.Requests and .Updaters to handle a session-based timout system. On each server request via Ajax there is a check whether the user hasn''t made something for the last x minutes, and if he hasn''t, the php page throws an 403 forbidden header (via header("HTTP/1.1 403 Forbidden")). I am

Gordon Messmer wrote: > On 12/15/2015 10:42 AM, m.roth at 5-cent.us wrote: >> How do you restart Xorg? I can't find a target for it, and restarting >> graphical.target doesn't seem to do it. > > Restart gdm. Really? There's no systemd target to restart it, and graphical.target doesn't do it? Um..... mark

> From: Reindl Harald > > besides that you did not provide the info "embedded system" - > when you > have systemd you also have "systemctl restart > whatever.service" and in > PHP it would be passthru('command') > > you don't know how you restart a service via CLI - seriously? I know how to do it through systemctl, but I was

Hello, On my new CentOS 7 server httpd stops running after about two minutes or so. strace shows me the process is asking for a password, and failing to get one, times out. In reading the docs I see an option to systemd: --no-ask-password. Can anyone tell me where and how to set this? As a workaround, I added "KillMode=none" to httpd.service, but I'd rather use the option to

I am running CentOS 7 on an outbound gateway server running Postfix.? I have a couple of cron jobs I was expecting to see in my email that never showed up.? It turns out that they were delivered to root, which is restricted on our exchange server, instead of the address I defined.? Please help. # cat /etc/crontab SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=ecssupport at

On 5 Apr 2020, at 21:20, Tobias Kirchhofer wrote: >>>> we experience difficulties with crond behaviour sending mail since >>>> CentOS 8.1. The cron job is the same like we used in CentOS 7. > > Meanwhile we found the reason for the bug - actually we do not know if > it is related to a specific version of CentOS or a specific kind of > command as cron job.

Anything interesting in the logs? sudo journalctl -xf _SYSTEMD_UNIT=crond.service