On 24 July 2013 14:55, Paul Eggleton paul.eggle...@linux.intel.com wrote:
Would it work to simply check for any files instaled into systemd_unitdir?
Agreed - the list of file types has grown over time so we'd been
constantly chasing systemd, and it's not like anything else is dropped
into this
On 07/25/2013 02:56 PM, Burton, Ross wrote:
On 24 July 2013 14:55, Paul Eggleton paul.eggle...@linux.intel.com wrote:
Would it work to simply check for any files instaled into systemd_unitdir?
Agreed - the list of file types has grown over time so we'd been
constantly chasing systemd, and it's
On 07/23/2013 06:03 PM, Shakeel, Muhammad wrote:
From: Muhammad Shakeel muhammad_shak...@mentor.com
If systemd is supported DISTRO_FEATURE and sysvinit is not and also if
systemd_unitdir contains a service file(s) then no need to keep init.d scripts
for sysvinit compatibility.
Signed-off-by:
On 07/23/2013 03:46 PM, Enrico Scholz wrote:
Shakeel, Muhammad
muhammad_shakeel-nmggyn9qbj3qt0dzr+a...@public.gmane.org writes:
If systemd is supported DISTRO_FEATURE and sysvinit is not and also if
systemd_unitdir contains a service file(s) then no need to keep init.d scripts
for sysvinit
On Wednesday 24 July 2013 18:22:11 Muhammad Shakeel wrote:
On 07/23/2013 03:46 PM, Enrico Scholz wrote:
Shakeel, Muhammad
muhammad_shakeel-nmggyn9qbj3qt0dzr+a...@public.gmane.org writes:
If systemd is supported DISTRO_FEATURE and sysvinit is not and also if
systemd_unitdir contains a
From: Muhammad Shakeel muhammad_shak...@mentor.com
If systemd is supported DISTRO_FEATURE and sysvinit is not and also if
systemd_unitdir contains a service file(s) then no need to keep init.d scripts
for sysvinit compatibility.
Signed-off-by: Muhammad Shakeel muhammad_shak...@mentor.com
---
Shakeel, Muhammad
muhammad_shakeel-nmggyn9qbj3qt0dzr+a...@public.gmane.org writes:
If systemd is supported DISTRO_FEATURE and sysvinit is not and also if
systemd_unitdir contains a service file(s) then no need to keep init.d scripts
for sysvinit compatibility.
...
+for filename
