Hello,
On 11/23/2016 03:52 PM, Reindl Harald wrote:
> so why do you strip the whole context and rest of the response?
>
> what is your exactly problem?
>
I think my original question on this thread is clear.
> it should be no rocket science to define a service, order starting as
> needed which
Hello,
On 11/23/2016 07:26 PM, Andrei Borzenkov wrote:
> Recent (for suitable definition of "recent") SAP releases are using
> sapcontrol framework to start/stop SAP services. So start startsap
> actually does, is to make remote procedure call to sapstartsrv which
> then starts SAP instance
Hello,
On 11/24/2016 12:22 AM, Lennart Poettering wrote:
> In general, while systemd provides a large degree of SysV compat, in
> the end we aren't SysV and thus we do not provide 100%. In cases like
> this this becomes visible.
You are 100% right :-)
Right after upgrading my first server,
I
Am Thu, 24 Nov 2016 10:39:52 +0100
schrieb Benoit SCHMID :
> Hello,
>
> On 11/23/2016 03:52 PM, Reindl Harald wrote:
> > so why do you strip the whole context and rest of the response?
> >
> > what is your exactly problem?
> >
> I think my original question on this
24.11.2016 18:20, Benoit SCHMID пишет:
> Hello,
>
> We have defined the following sap_XXX.service.
> It contains the following in [Unit]:
> ###
> After=local-fs.target network-online.target ora_lsnr_XXX.service
> remote-fs.target
> Wants=ora_lsnr_XXX.service
> ###
>
> Stopping and Starting the
Am Wed, 23 Nov 2016 09:14:34 +0100
schrieb Cédric BRINER :
> Hi,
>
> For the context, we are trying to stop a daemon launched by a user...
>
> >> Hi,
> >>
> >> sapRunning service contains a "After=user.slice". But at the
> >> shutdown, a process (write-sysv-test.pl)
Hello,
On 11/24/2016 08:14 PM, Andrei Borzenkov wrote:
What is blkdeactivate? It does not belong to systemd.
You are asking too much, for me, Andrei because it comes from RH repo :-)
I have found this on my host:
# cat /usr/lib/systemd/system/blk-availability.service
[Unit]
On Thu, 24 Nov 2016, Kai Krakow wrote:
Am Wed, 23 Nov 2016 09:14:34 +0100
schrieb Cédric BRINER :
Hi,
For the context, we are trying to stop a daemon launched by a user...
Hi,
sapRunning service contains a "After=user.slice". But at the
shutdown, a process
25.11.2016 00:50, Benoit SCHMID пишет:
> Hello,
>
>
> On 11/24/2016 08:14 PM, Andrei Borzenkov wrote:
>> What is blkdeactivate? It does not belong to systemd.
>
> You are asking too much, for me, Andrei because it comes from RH repo :-)
>
Well, it appears it is part of LVM2.
Version 2.02.98
On Thu, 24.11.16 10:59, Benoit SCHMID (benoit.sch...@unige.ch) wrote:
> Hello,
>
> On 11/24/2016 12:22 AM, Lennart Poettering wrote:
> > In general, while systemd provides a large degree of SysV compat, in
> > the end we aren't SysV and thus we do not provide 100%. In cases like
> > this this
Hello,
We have defined the following sap_XXX.service.
It contains the following in [Unit]:
###
After=local-fs.target network-online.target ora_lsnr_XXX.service
remote-fs.target
Wants=ora_lsnr_XXX.service
###
Stopping and Starting the service with systemd runs fine.
When we reboot, systemd
Am 24.11.2016 um 16:20 schrieb Benoit SCHMID:
We have defined the following sap_XXX.service.
It contains the following in [Unit]:
###
After=local-fs.target network-online.target ora_lsnr_XXX.service
remote-fs.target
Wants=ora_lsnr_XXX.service
###
Stopping and Starting the service with systemd
Hello,
On 11/24/2016 04:42 PM, Reindl Harald wrote:
>
> you *really* should post the whole systemd-unit instead pieces!
> have you played around with DefaultDependencies?
Here it is :-)
[Unit]
Description=SAP XXX
After=local-fs.target network-online.target ora_lsnr_XXX.service
remote-fs.target
13 matches
Mail list logo