Working with :

<?php



///////////////////////////////////////////////////////////////////////////////

// B O O T S T R A P

///////////////////////////////////////////////////////////////////////////////



$bootstrap = getenv('CLEAROS_BOOTSTRAP') ? getenv('CLEAROS_BOOTSTRAP') : '/usr/clearos/framework/shared';

require_once $bootstrap . '/bootstrap.php';



///////////////////////////////////////////////////////////////////////////////

// T R A N S L A T I O N S

///////////////////////////////////////////////////////////////////////////////



clearos_load_language('samba_common');



///////////////////////////////////////////////////////////////////////////////

// C O N F I G L E T

///////////////////////////////////////////////////////////////////////////////



$configlet = array(

        'title' => 'rtorent',

        'package' => 'rtorrent',

        'process_name' => 'rtorrent',

        'pid_file' => '/home/rtorrent/temp/rtorrent.pid',

        'reloadable' => FALSE,

        'url' => ''

);

but as far as I discovered the file name must match service name... and file content is not important

Hi,

What is the purpose of each attributes ?

        'title' => 'Monitorix',

        'package' => 'monitorix',

        'process_name' => 'monitorix',

        'pid_file' => '/var/run/monitorix.pid',

        'reloadable' => FALSE,

        'url' => '/monitorix'

I could easely understand tittle & process_name.
But what is package for ?
reloadable boolean ?
url ?
If service do not have any .pid file could we leave pid_file blank ? Or do we need to find a substitute ?

You need to drop a 'configlet' into:

/var/clearos/base/daemon

The name of the file *must* be the name of the init script with .php extension. For example, rsyslog.php.

Here's an example of one so you can use it as a template to create your own. The only difference I'd suggest is that you hardcode the title since the base language template will get stomped on with updates. Eg.

'title' => 'My Friendly Service Name',

B.