Administration groups: Defining a group

Next Previous Contents

## 2. Defining a group

Here are the steps to create an administration group.

## 2.1 Give it a name

Each group must have a uniq name. The name must not have any space. Each group correspond to a sub-directory in

> `

>             /etc/linuxconf/admgroups

> `

The name of the sub-directory is simply the group name.

## 2.2 Give it a description

This is used to enhance various screens. It has no functional usage.

## 2.3 Link it with an administration tree

An administration tree is like a virtual workstation in your computer. It has all the configuration files (or could have) a fully configured linux station normally have. By linking to a specific administration tree you are telling that this administration group is picking its configuration files (or parts of) from the configuration files of this administration tree.

The idea of separating the administration tree from the administration group is that, in many environment, you will have one administration tree and the machines part of this environment will split this way

- Most machines: They share a large part of the administration tree.
- Some machines: They share the same information except for specific services only.
- Some other machines: They are completely independent. As such they are not member of any administration group.

Often, all machines of the same physical network will share some aspect of a single administration tree.

A help list shows available administration trees. You can enter a name which is not in the list. Just don't forget to create it later.

### The / administration tree

It is possible to share the configuration of the workstation itself. The administration tree is simply called /. It is shown in the help list.

## 2.4 Members of the group

You simply enumerate the various members (the machine name and domain) who must be synchronized. This is currently limited as you have to specify them one by one. This is expect to expand in various area:

- Allow the definition of pseudo member which will themselves repeat the configuration file to other machines. A repeater may act this way for several administration group.
- Allow for usage of wild cards: *.domain.com.
- Allow for usage of network/netmask pairs.
- Allow for on demand supply of configuration files. As such and administration group may very well have no official members!

## 2.5 Sub-system to share

A list of all sub-systems available is presented. On the left, the sub-system ID is presented. On the right, the description of the sub-system is presented. For each sub-system, there is a check-box. You can select this way which sub-systems are shared.

Next Previous Contents