[
https://issues.apache.org/jira/browse/BIGTOP-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886190#comment-13886190
]
Konstantin Boudnik commented on BIGTOP-1097:
--------------------------------------------
I just checked Fedora 15 and the output of service status command is like
{noformat}
[root@localhost ~]# service crond status
Redirecting to /bin/systemctl status crond.service
crond.service - Command Scheduler
Loaded: loaded (/lib/systemd/system/crond.service)
Active: active (running) since Thu, 31 Oct 2013 08:05:50 -0400; 2
months and 29 days ago
Main PID: 853 (crond)
CGroup: name=systemd:/system/crond.service
└ 853 /usr/sbin/crond -n
{noformat}
So, 2nd line won't work on it too.
> introduce bigtop-groovy package
> -------------------------------
>
> Key: BIGTOP-1097
> URL: https://issues.apache.org/jira/browse/BIGTOP-1097
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.6.0
> Reporter: Roman Shaposhnik
> Assignee: Konstantin Boudnik
> Fix For: 0.8.0
>
> Attachments: BIGTOP-1097.patch
>
>
> Bigtop platform depends on groovy extensively and we see a trend to introduce
> new functionality into the cluster deployment, etc. that will greatly benefit
> from the presence of a dynamic, functional scripting language on top of JVM.
> Hence, it makes sense to provide Groovy runtime environment as a part of
> Bigtop installable stack (e.g. think of bigtop-utils type of package). It
> will be lightweight and only needs to include a couple of jar files from a
> standard Groovy distribution. There's no need to build Groovy from scratch
> but just download the binary archive, extract jars we need, and wrap them
> into a Linux package.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
