Re: [systemd-devel] sd-bus: serving method call message in a separate thread

2019-03-04 Thread Giacinto Cifelli
Hi Stanislav, On Mon, Mar 4, 2019 at 9:56 PM Stanislav Angelovič wrote: > > Hi sd-bus-ers! > > Quick question: How can I process a method call on service side in a > different thread, without creating race condition? > > Longer version: > > In sdbus-c++, we are working on server-side asynchronou

[systemd-devel] sd-bus: serving method call message in a separate thread

2019-03-04 Thread Stanislav Angelovič
Hi sd-bus-ers! Quick question: How can I process a method call on service side in a different thread, without creating race condition? Longer version: In sdbus-c++, we are working on server-side asynchronous method call support. In sd-bus, a service handles D-Bus method calls via sd_bus_message

Re: [systemd-devel] OnCalendar timer starts before the scheduled date has passed

2019-03-04 Thread Alden Page
You're right, I misunderstood the purpose the the Requires directive. Thanks for pointing this out, I am seeing the expected behavior in my script after removing it. Alden On Mon, Mar 4, 2019 at 1:43 PM Andrei Borzenkov wrote: > 04.03.2019 21:19, Alden Page пишет: > > Hi systemd team, > > > > I

Re: [systemd-devel] OnCalendar timer starts before the scheduled date has passed

2019-03-04 Thread Andrei Borzenkov
04.03.2019 21:19, Alden Page пишет: > Hi systemd team, > > I'm having some trouble understanding the behavior of a systemd timer I've > set up in systemd version 219. I have a task that I want to run once per > week on Sundays at 3:00am UTC. However, as soon as I do `systemctl start > my_timer.tim

[systemd-devel] OnCalendar timer starts before the scheduled date has passed

2019-03-04 Thread Alden Page
Hi systemd team, I'm having some trouble understanding the behavior of a systemd timer I've set up in systemd version 219. I have a task that I want to run once per week on Sundays at 3:00am UTC. However, as soon as I do `systemctl start my_timer.timer`, the task starts no matter what time it is.

Re: [systemd-devel] what does it mean to have exit-code of 251

2019-03-04 Thread prashantkumar dhotre
Thanks. It seems like that call to zookeeper lib API is causing this exit with 251 and hence it is most likely in zookeeper lib code. Regards On Mon, Mar 4, 2019 at 5:26 PM Lennart Poettering wrote: > On Mo, 04.03.19 16:58, prashantkumar dhotre (prashantkumardho...@gmail.com) > wrote: > > > Hi,

Re: [systemd-devel] what does it mean to have exit-code of 251

2019-03-04 Thread Lennart Poettering
On Mo, 04.03.19 16:58, prashantkumar dhotre (prashantkumardho...@gmail.com) wrote: > Hi, > > In my journal log, I see ; > > 1199473 Mar 01 15:46:03 evo-qfx-01 systemd[1]: ifmand.service: Main process > exited, code=exited, status=251/n/a > > > I want to know what does 251 means. > > Can you plea

Re: [systemd-devel] what does it mean to have exit-code of 251

2019-03-04 Thread prashantkumar dhotre
In my app, I don't explicitly call exit(251). I use zookeeper lib. Fro my logs,I see that after a call to zookeeper lib API, I see that my service exited with 251. Is 251 a std exit code or app/lib specific custom exit code ? Thanks On Mon, Mar 4, 2019 at 5:02 PM Umut Tezduyar Lindskog wrote:

Re: [systemd-devel] what does it mean to have exit-code of 251

2019-03-04 Thread Umut Tezduyar Lindskog
You need to do some bit analysis - https://shapeshed.com/unix-exit-codes/ On Mon, Mar 4, 2019 at 12:29 PM prashantkumar dhotre wrote: > > Hi, > > In my journal log, I see ; > > 1199473 Mar 01 15:46:03 evo-qfx-01 systemd[1]: ifmand.service: Main process > exited, code=exited, status=251/n/a > > >

[systemd-devel] what does it mean to have exit-code of 251

2019-03-04 Thread prashantkumar dhotre
Hi, In my journal log, I see ; 1199473 Mar 01 15:46:03 evo-qfx-01 systemd[1]: ifmand.service: Main process exited, code=exited, status=251/n/a I want to know what does 251 means. Can you please let me know where can I see the exit-code to meaning mapping ? Thanks Prashant _