2018-01-23 23:43 GMT+01:00 Danny Milosavljevic <[email protected]>:
> The attached file is gnu/services/trytond.scm which successfully runs > trytond. > With "successfully"" you mean that it connects to postgres and it shhows te proper screens in the client ? Sometimes the trytond daemon does run but it fails to connect to postgres I'll check this out. Only, not today, neither tomorrow probably. But I will, sooner or later Thanks ! > Everyone: > > After I've tried writing some shepherd service I have to say that writing a > shepherd "start" action is way too difficult. > > Even now, I've not gotten to work: > > * Having the activation depend on any other service. > * Logging errors from start-trytond to stderr or stdout. > As far as I understand make-forkexec-constructor takes special care not > to kill stderr. As long there's no log-file specified it should leave > stdout > and stderr alone. So where does the text go? > > I've had other problems like: > > * root's shepherd hangs sometimes and herd can't connect to it anymore. > * When I use (error "XXX") in a shepherd start block, booting the system > drops me into a REPL and doesn't let me out again (instead of just failing > this one service and continuing to boot). > > Sigh... > I'm relieved that someone else finds this difficult Thans again !
