On 07/08/2014 03:21 PM, Reindl Harald wrote:
>
> Am 08.07.2014 18:17, schrieb Robert Moskowitz:
>> On 07/08/2014 11:05 AM, Russell Miller wrote:
>>> Even its sysv compatibility is incomplete. It runs sysv scripts, but in such a
>>> way as to break any but the simplest. I've run into situations where I've actually
>>> had to make a systemd unit because it broke the script, and I couldn't fix it. The
>>> script was fine, ran perfectly if you just ran it, and systemd did... *something*...
>>> to it. I still haven't figured out what. And debugging is an absolute pain.
>> I am also struggling with this and the HIPL code (on F20). If you just
>> start the services, it takes about 5 min to complete. If you just run
>> the programs and tell them to drop into the background it is a handful
>> of seconds. Strip out comments from the script and it starts right up
>> with systemctl. Huh? What is going on? I was told that systemctl does
>> seem to try and make 'sense' out of comments...
> so why do you not write a simple systemd-unit starting your shellscript?
>
>
> [root@testserver:~]$ cat /usr/lib/systemd/system/zram.service
> [Unit]
> Description=Enable compressed swap in memory using zram
>
> [Service]
> RemainAfterExit=yes
> ExecStart=/usr/sbin/zram.sh start
> ExecStop=/usr/sbin/zram.sh stop
> Type=oneshot
>
> [Install]
> WantedBy=multi-user.target
>
partially because I am the tester, not the developer. I found the
problem, though.
So I will pass this on to the developers.
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
