Jump to contentJump to page navigation: previous page [access key p]/next page [access key n]
Applies to SUSE Linux Enterprise Point of Service 11 SP3 and SUSE Linux Enterprise Point of Service 12 Image Server

B Point of Service Commands

In a SUSE® Linux Enterprise Point of Service system, several commands are provided to initialize and maintain Administration and Branch Servers. This section describes these commands and their usage.

B.1 Overview

All the programs required to manage the system and to generate configuration files are implemented in Perl and as shell scripts. All the file names contain the prefix pos, so a quick overview of the available programs can be displayed using tab completion.

It is recommended to use the /usr/sbin directory as the storage location for the SUSE Linux Enterprise Point of Service scripts. All the scripts can be controlled transparently using the posAdmin meta script, as long as they are not run by cron. The posAdmin script is designed to operate in the same way on the Administration Server as on the Branch Servers.

The basic mechanism for all actions (image transfer to a Branch Server, data readout from the directory) is a pull mechanism from the Branch Servers that is run directly on the Branch Servers. One important element is the central logging of all actions with success or failure flags on the Administration Server. For all actions, the rule must be transaction security or atomic execution to avoid inconsistent configuration files, for example.

B.2 Core Script Process

When Point of Service terminals are being set up in a branch or subsidiary, the posleases2ldap script must be started as a daemon on the Branch Server for the relevant branch. All other scripts are controlled by this script.

The interplay of scripts on the Branch Server works as follows:

  1. posleases2ldap is started directly on the Branch Server. If the scDynamicIp attribute is not set to TRUE in the relevant scLocation, the script immediately terminates.

  2. posleases2ldap is running as a daemon process and monitors the /var/lib/dhcp/db/dhcpd.leases file for changes. The script detects in which scLocation (branch) it is running, reading the IP address of the server.

  3. If role mode is enabled or scIdPool is not empty, posleases2ldap periodically updates rolelist and idlists according to the LDAP database.

  4. If posleases2ldap finds MAC addresses in the leases that are not yet entered in the directory, it generates new entries for the scWorkstation object class under the relevant scLocation object. The first items filled out are the required attributes macAddress, ipHostNumber, and the cn for the entry. The terminal's IP address and name are automatically generated, and the MAC address is taken from the leases file. These entries are like an outline.

  5. The upload directory on the TFTP server is searched for files of the pattern hwtype.MAC or hwtype.MAC.hash that are being uploaded by Point of Service terminals registered from the DiskNetboot system. The Point of Service hardware type is specified in these files. For more information, see Section 6.4, “Booting the Point of Service Terminal”. If any files of this type are found, the following process runs:

    • Using the MAC address, the relevant scWorkstation entry is looked up in the LDAP directory. With the content of the hwtype.MAC file, the corresponding scRefPc (the reference hardware type in the global container) is searched. In the scRefPc object (named after the hardware type), the image type for this hardware type is specified as a reference to a scPosImage object in the attribute scPosImageDn, which points to the reference image in the global container. The information about the reference hardware and image are then added to the scWorkstation object as distinguished names (DN) and the attributes are named scRefPcDn and scPosImageDn.

    • All information is collected to generate the /srv/tftpboot/KIWI/config.MAC configuration file. It is possible to specify hardware type or image type dependent configuration files, such as xorg.conf, which is hardware type dependent. These files are generated in the/srv/tftpboot/KIWI/MAC directory. For this purpose, an object of the class scConfigFileTemplate can be added to the relevant scRefPc or scPosImage object in the global container.

      At this point, the scConfigFileData attribute of the scConfigFileTemplate object contains the required file. Hardware or image dependent configuration files are always looked up by the hardware order image.

      All newly generated files are initially named with the prefix TMP_.

    • The configuration files are renamed from TMP_* to their final names. The /srv/tftpboot/upload/hwtype.MAC.HASH file is deleted. The registration of a newly detected Point of Service terminal is complete.

  6. posleases2ldap starts posldap2dns. The zone files for the DNS server are regenerated from the directory data as a temporary file and renamed. The DNS service is restarted if there are any changes.

  7. posleases2ldap starts posldap2dhcp. The dhcpd.conf file is regenerated from the directory data as a temporary file and renamed. The DHCP service is restarted if there are any changes.

  8. posleases2ldap runs in a loop starting at Step 2 until it is terminated or the scDynamicIp attribute in the scLocation object for the branch is set to FALSE.

  9. posleases2ldap starts the ImageNotify daemon, which monitors /srv/tftpboot/upload for boot version, MAC address files, and transfers image notification data to LDAP.

B.3 Command Quick Reference

The remainder of this section provides a brief explanation of each SUSE Linux Enterprise Point of Service command, its function, and usage.

B.3.1 posNetworkInit

posNetworkInit is a helper script that finds the Branch Server network configuration in LDAP, and depending on the situation, updates either the Branch Server network configuration or the LDAP database. If successful, posNetworkInit prints the Branch Server's network details.

B.3.1.1 Function

posNetworkInit is used mainly within posInitBranchServer to determine the Branch Server network configuration and to update the network configuration and resolver (/etc/resolv.conf).

B.3.1.2 Usage

posNetworkInit [--ldapDev device] [--force] [device]
Table B.1: posNetworkInit Options

Option

Description

device

If more NICs exist on the Branch Server, choose the NIC with a name equal to the device.

--force

Forces reconfiguration of the NIC if the NIC is configured differently than in LDAP.

--ldapDev device

If more than one scNetworkcard object is defined in LDAP, choose the scNetworkcard with scDevice equal to the device.

B.3.2 posInitBranchserver

The purpose of posInitBranchserver is to generate the central configuration file for all other SUSE Linux Enterprise Point of Service commands. It is used on a Branch Server to configure the internal network, to generate configuration files for the DNS, DHCP and TFTP services, to activate the DNS, DHCP, TFTP and posLeases services at boot time, and to start the services if specified in LDAP.

B.3.2.1 Function

When running this command, you are prompted to enter the organization/company name, country abbreviation, IP address, and the LDAP administrator password of the Administration Server. The /etc/SLEPOS/branchserver.conf configuration file is generated by filling in the LDAP base, LDAP administrator password, and the FQDN of the Administration Server. The /etc/SLEPOS/template/branchserver.conf.template file is used as a template.

The posInitBranchserver command uses posNetworkInit to find internal network details in LDAP and update /etc/resolv.conf with basic DNS information. The posNetworkInit command also yields the domain name for this branch, which is used to generate proper configuration header files for the DHCP and DNS services, which in turn are needed for posldap2dns and posldap2dhcp scripts.

Branch Server services are then configured based on settings in LDAP. The Branch Server service is run and set to start at boot time only when attribute scServiceStatus is TRUE under its respective scService entry in LDAP.

For compatibility reasons, Branch Server checks LDAP if a posLeases service configuration exists. If not, the service is added to LDAP based on default values (scPosleasesChecktime set to 5 seconds, scPosleasesTimeout set to 60 seconds, and scPosleasesMaxNotify maximum of 6 boot notifications). Also, the scServiceStatus is set to FALSE.

DNS is only configured when the appropriate service is available in LDAP. The zone file header for posldap2dns is generated from /etc/SLEPOS/template/dns-zonefile.header.template and written to /etc/named.d/ldap_generated/dns-zonefile.header. The posldap2dns script then configures the rest of the DNS system. Proper DNS forwarder mode is set in Netconfig and the DNS service is started if enabled in LDAP.

DHCP service is only configured when the appropriate service is available in LDAP. After preparing dhcp.conf.header file, posldap2dhcp configures the rest of the DHCP service. Sysconfig is used to set the DHCP listening interface and chroot settings. Then the DHCP service is started if enabled in LDAP.

A multicast route is persistently set up. Sysconfig is used to set the TFTP listening address, directory and user. The rest is configured by the posldap2pxe script. Then the TFTP service is started if enabled in LDAP.

FTP service is available on the Branch Server. If enabled in LDAP, the service is configured based on the supplied template and started.

The rsync service is the only service which does not have an LDAP entry and is always configured and started.

Note
Note: Registration of Terminals After Branch Server Change

When the Branch Server is changed (for example reinstalled) and terminals are still registered in LDAP, but no longer have the associated /srv/tftpboot/KIWI/config.MAC files available, these terminals will be reregistered by posleases2ldap when they upload the hwtype.MAC.hash file. Alternatively, you can use posldap2crconfig --dumpall to re-create all config.MAC files for all registered workstations. The only difference is that in case of a non-role-based approach (legacy), the --dumpall method will honor a customized scRefPcDn cash register reference (even if the referred cash register is not associated to the workstation's scPosRegisterBiosVersion). On the contrary, during the registration update via the uploaded hwtype.MAC file, the standard registration workflow is used. This means that scRefPcDn will be set to a cash register conforming to the workstation's scPosRegisterBiosVersion, or to a default one if not found.

posInitBranchserver only works correctly if the Branch Server data in LDAP has been created properly in advance using the posAdmin tool after the installation of the Administration Server. For further information, refer to Section 4.6.2, “Creating Point of Service Terminal Objects in LDAP”.

B.3.2.2 Usage

Run posInitBranchserver on a Branch Server.

Table B.2: posInitBranchserver Options

Option

Description

-r or --reinitialize [=FILE]

Reinitializes the Branch Server, default values are loaded from an existing Branch Server configuration file or from a file specified by FILE.

-f or --file =FILE

Specifies the path to the SUSE Linux Enterprise Point of Service offline installation file for offline initialization.

-n or --noninteractive

Performs unattended installation (-f or -r options are needed to specify source of information).

-p or --chpasswd

Change Branch Server LDAP password, Branch Server must be already initialized.

-V or --version

Displays the version of the script being used.

-h or --help

Displays available options and their description.

--usage

Displays basic usage information.

B.3.2.3 Files

/etc/SLEPOS/named/named.conf
/etc/SLEPOS/template/dhcpd.conf.header.template
/etc/SLEPOS/template/dns-zonefile.header.template
/etc/named.d/ldap_generated/dns-zonefile.header
/etc/SLEPOS/dhcpd/dhcpd.conf.header
/etc/SLEPOS/template/resolv.conf.template
/etc/resolv.conf
/etc/sysconfig/network/routes
/etc/sysconfig/network/config
/etc/sysconfig/dhcpd
/etc/sysconfig/atftpd

B.3.3 posInitAdminserver

The purpose of posInitAdminserver is to configure the OpenLDAP directory server software and to create the initial data in the LDAP directory. You are prompted to enter the organization/company name, country abbreviation, and the LDAP administration password. You can also enable or disable SSL communication. Company name and country abbreviation are used to compose the LDAP base DN in the form o=myorg,c=us.

Note
Note: posInitLdap.sh

In previous SUSE Linux Enterprise Point of Service versions, posInitAdminserver was called posInitLdap.sh, which is now a symbolic link to the posInitAdminserver command.

B.3.3.1 Function

posInitAdminserver uses /etc/SLEPOS/template/slapd.conf.template to create the OpenLDAP configuration file /etc/openldap/slapd.conf. The LDAP base DN and password are replaced from the posInitAdminserver command with the corresponding user entries. After generating the configuration file, the OpenLDAP service is started.

posInitAdminserver then uses the template file /etc/SLEPOS/template/ldif.pos.template to create an LDAP data file /etc/SLEPOS/template/ldif.pos, which it then imports into the LDAP directory. Now the initial LDAP directory structure is available on the Administration Server.

posInitAdminserver uses posReadPassword.pl when the password is entered to hide the password characters.

B.3.3.2 Usage

Run posInitAdminserver on an Administration Server.

Table B.3: posInitAdminserver Options

Option

Description

--regenerate

Forces regeneration of SSL certificates. Old certificates are deleted. This option should only be used for SSL. Default is not to regenerate.

-r or --reconfigure =FILE

Reconfigures the Administration Server with the provided configuration file.

-n or --noninteractive

Performs unattended installation (-f or -r options are needed).

-V or --version

Displays the version of the script being used.

-h or --help

Displays available options and their description.

--usage

Displays basic usage information.

Warning
Warning

Running this command destroys any existing data in LDAP.

B.3.3.3 Files

/etc/openldap/ldap.conf
/etc/openldap/slapd.conf
/etc/SLEPOS/template/slapd.conf.template
/etc/init.d/ldap
/etc/SLEPOS/template/openldap.template
/etc/SLEPOS/template/ldif.pos.template

B.3.4 posldap2crconfig

posldap2crconfig is now a link to provide backward compatibility. It triggers pos. If used with --dumpall, it is equivalent to the pos dump-all command. If used alone, a single registration cycle is executed by calling posleases2ldap -o -d.

B.3.4.1 Function

See Section B.2, “Core Script Process” for a detailed description of posleases2ldap.

B.3.4.2 Usage

posldap2crconfig [--dumpall]

B.3.4.3 Files

/etc/SLEPOS/branchserver.conf

B.3.5 posldap2dhcp

posldap2dhcp generates the DHCP daemon configuration file from LDAP.

B.3.5.1 Function

posldap2dhcp is called by posleases2ldap at regular intervals. First, all scLocation objects are looked up in LDAP. Each of these objects defines a subnet and for each of them a subnet declaration in the dhcpd.conf is generated.

The header zone file is taken from the file specified in the configuration file directive LDAP2DHCP_TEMPLATEFILE, which is /etc/SLEPOS/dhcpd/dhcpd.conf.header by default. The content of the header file is adapted to the installation by posInitBranchserver (see Section B.3.2, “posInitBranchserver”).

The value of the scDhcpRange attribute in an scLocation object is translated into a range statement in the subnet declaration.

In addition, the options for tftpboot are written into each subnet declaration. For each scCashRegister, a fixed address declaration is generated.

The new dhcpd.conf file is first generated in a temporary directory. If it differs from the working version, dhcpc is run with the temporary file in check mode. If it passes the check, it is copied over the working file and the command to restart the DHCP daemon is returned to be executed by posleases2ldap.

The dhcp.conf file now allows persistent customizations. During the Branch Server initialization and when posldap2dhcp is run, the dhcp.conf file is rewriten from templates. However during normal operations, when a workstation is registered by posleases2ldap or its configuration is dumped by pos dump-* commands, the dhcp.conf file is only modified by adding or removing host entries. These are confined within a SUSE Linux Enterprise Point of Service area marked by '##_POS_group_start' and '###_POS_group_end#' comments. These comments, and the structure within them, should not be altered, or SUSE Linux Enterprise Point of Service registration will not work. However all other data in the dhcp.conf can be freely modified or extended and customized, provided the whole file still forms a valid configuration.

B.3.5.2 Usage

posldap2dhcp is called by posleases2ldap.

B.3.5.3 Files

/etc/SLEPOS/branchserver.conf
/etc/dhcpd.conf -> /etc/SLEPOS/dhcpd/dhcpd.conf
/etc/SLEPOS/dhcpd/dhcpd.conf.header

B.3.6 posldap2dns

posldap2dns generates DNS configuration and zone files from LDAP.

B.3.6.1 Function

posldap2dns is called by posleases2ldap at regular intervals. First, all scLocation objects are looked up in LDAP. Each of these objects defines a subnet and for each of them a zone file is created.

The header of each zone file is taken from the file specified in the configuration file directive POS_LDAP2DNS_ZONETEMPLATE, which is /etc/named.d/ldap_generated/dns-zonefile.header by default. The content of the zone file header is adapted to the installation by posInitBranchserver (see Section B.3.2, “posInitBranchserver”).

The value of the scDhcpRange attribute in an scLocation object is translated into a \$GENERATE directive. For each scService or scHAService, an A record is created or, if multiple objects of that kind point to the same IP address, a CNAME record. After that, an A record for each Point of Service terminal is generated.

Finally, the /etc/named.d/ldap_generated/named.zones file containing the definitions of all generated zones is created. It is included from within /etc/named.conf. If zones were changed, posldap2dns returns the appropriate commands to restart the DNS service. The commands are executed by posleases2ldap.

B.3.6.2 Usage

posldap2dns is called by posleases2ldap.

B.3.6.3 Files

/etc/SLEPOS/branchserver.conf
/etc/named.d/ldap_generated/
/etc/named.d/ldap_generated/dns-zonefile.header
/etc/named.d/ldap_generated/named.zones
/etc/named.conf

B.3.7 posleases2ldap

posleases2ldap registers new Point of Service terminals in LDAP and transfers image install notification data to LDAP. It also triggers posldap2crconfig.

B.3.7.1 Function

See Section B.2, “Core Script Process” for a detailed description of posleases2ldap.

Point of Service boot process
Figure B.1: Overview of the posleases2ldap Workflow

B.3.7.2 Usage

In normal operation, posleases2ldap is run as a daemon. It can be started by using the /etc/init.d/posleases2ldap init script, which is also used to start the daemon at boot time. To enable this, use chkconfig posleases2ldap on.

If posleases2ldap is started manually, it immediately runs in the background. To avoid this, use the optional parameter -d. If started this way, posleases2ldap stops when the shell is closed.

B.3.7.3 Files

/etc/SLEPOS/branchserver.conf
/srv/tftpboot/upload/hwtype.MAC.HASH

B.3.8 posReadPassword.pl

posReadPassword.pl is a helper script for the password entry that does not show the entered password.

B.3.8.1 Functions

posReadPassword.pl is called by posInitAdminserver, posInitEdir, and posInitBranchserver for password entry purposes.

B.3.8.2 Usage

In shell scripts, use a line such as

PASSWORD=`/usr/lib/SLEPOS/posReadPassword.pl`

B.3.8.3 Files

None.

B.3.9 possyncimages

The possyncimages command must be run on a Branch Server to download or update images from the Administration Server. It uses rsync and requires that the rsync service is properly configured and running on the Administration Server. This command can be run manually, but depending on your system requirements, you can create a cron job that runs the command every night to keep the images up to date.

B.3.9.1 Function

The possyncimages --remote command transfers the images from /srv/SLEPOS (images prepared by central administrator) on the Administration Server to /srv/SLEPOS on the Branch Server. It first downloads all available md5 files, then decides which images should be downloaded (as whole files or as deltas), then it runs rsync command for each image.

The possyncimages --local command transfers the images from /srv/SLEPOS on the Branch Server to /srv/tftpboot (images in production).

The possyncimages command without arguments performs both --remote and --local.

The list of downloaded images can be adjusted using the scSynchronizedImagesDn attribute. For more information, see Section 5.3.1, “Controlling the List of Images Downloaded by Branch Server”

B.3.9.2 Usage

Run possyncimages on a Branch Server or set up a cron job. It may be useful to handle possyncimages --remote with cron but perform possyncimages --local manually when necessary. A crontab line to run nightly at 1 AM might look like this:

0 1 * * * /usr/sbin/possyncimages  --remote

B.3.9.3 Files

/etc/SLEPOS/branchserver.conf

B.3.10 registerImages

The registerImages command is used to copy the Point of Service images to the rsync directory on the Administration Server.

B.3.10.1 Function

The registerImages command copies the system image files to the rsync directory on the Administration Server (/srv/SLEPOS). It also provides functions for compressing the images, adding them to LDAP and installing boot images.

The registerImages command only works properly when the Administration Server and Image Building Server are installed on the same machine. If this is not the case, the images must be copied to the Administration Server manually first. For more information, see Section 4.7.3, “Manually Copying Images to the Administration Server's rsync Directory”.

B.3.10.2 Usage

The registerImages command uses the following options:

-h or --help

Displays help.  

--gzip

Compress the image.  

--delta base_name-ver

Install also a delta (containing only necessary changes) image created against the given base.  

--move

Delete the source after successful installation.  

--no-hardlings

Do not use hard links, always copy files.  

--ldap

The corresponding LDAP entry.  

--luks password

Set the image password in LDAP.

--image_cn cn

The scPosImage cn. The default value is taken from the file name.  

--container_cn cn

The scDistributionContainer cn. The default value is default.  

--kernel path

The path to the kernel part of the boot image to install.  

--initrd path

The path to the initrd part of the boot image to install.  

--include-boot

Extract the boot image from the first system image.

-vlevel or --verbose=level

Set the stderr verbosity level. The verbosity level can be specified by a number or as one of the following values: emerg, alert, crit, err, warn, notice, info, debug.  

--syslog=level

Set the syslog verbosity level. The verbosity level can be specified by a number or as one of the following values: emerg, alert, crit, err, warn, notice, info, debug.  

B.3.11 posASwatch

The posASwatch service is used on Branch Servers to determine whether and when synchronization between Administration Server and Branch Server should be started. It is not needed when the Administration Server and Branch Server are configured on the same machine.

B.3.11.1 Function

The posASwatch service checks the availability of the Administration Server, the LDAP synchronization and replication, and the posleases2ldap core service.

B.3.11.2 Usage

On a Branch Server, run rcposASWatch start to start and rcposASWatch stop to stop the posASwatch service. To check the service status, use the rcposASWatch status command.

To ensure that the Branch Server starts the posASWatch command automatically at boot time, execute the insserv posASWatch command.

B.3.12 pos

Necessary LDAP objects can be created with posAdmin. You can also use pos, which is easier to use but less general.

B.3.12.1 Function

The pos command, depending on the subcommand used, easily creates necessary LDAP objects or reads improtant data from them.

B.3.12.2 Usage

The following commands are available:

pos help

Prints help.

pos id-list

Prints the ID list, one ID per line.

pos cr-list

Lists the registered cash register types.

pos image-list

Lists the registered images.

pos ws-list

Lists the registered workstations.

pos role-list

Lists roles. Can be used with --hide-local and --hide-global options to hide local or global roles.

pos id-add --id id

Adds a new ID id.

pos id-delete --id id

Deletes the ID id. If the --force option is used (pos id-delete --force --id id), the ID is deleted even if it is in use.

pos id-set --idid --workstation name or MAC

Assigns the ID id to the workstation specified by its LDAP name or MAC address.

pos role-create --cncn --role name --description description

Creates a new role. The --cn option specifies the LDAP CN of the new role. The --role specifies the role name that is shown to users. The --description specifies the role description that is shown to users.

pos role-add --cash-registercn or hwtype --image image --role cn or name

Copies the global cash register configuration to the given role and assigns the image to it. The --cash-register option identifies the source cash register by its CN or hardware type. The --image option specifies the image CN or name. The --role option specifies the role CN or name.

If used with the --force option, the target cash register is replaced if it exists.

pos role-cr-remove --rolecn or name --cash-register cn or hwtype

Removes a copy of the given cash register from the given role. The --role option specifies the role by its CN or name. The --cash-register option identifies the source cash register by its CN or hardware type.

pos role-delete --role role cn or name

Deletes a role.

pos role-for-ws --rolesrole1[,role2,...] [--workstation] name or MAC[,name or MAC,...]

Sets the list of allowed roles for a given workstation. The workstation is specified by its LDAP name or MAC address.

pos role-set --rolerole [--workstation] name or MAC[,name or MAC,...]

Assigns the given role to the given workstation. The --workstation option specifies the workstation by its name or MAC address. The --role option specifies the role by its cn or name.

pos dump-ws [--workstation]name or MAC[,name or MAC...]

Writes config.MAC for the given workstation. The --workstation option specifies the workstation by its name or MAC address.

pos dump-lists

Writes the role and ID lists, and refreshes the default PXE file.

pos dump-all

Writes the role, ID lists, default PXE and config.MAC, with specific PXE if needed, for all the workstations.

pos remap-all

Updates LDAP registration (ID to DNS and IP mapping) for all workstations. Should be used if scDnsMapFunc or scIpMapFunc was changed.

pos sync [start|stop|status]

Starts, stops, or checks LDAP synchronization between Administration Server and Branch Server.

pos pxe-bootmenu --set [--imagespath <custom boot image directory>] [--force]

Installs PXE menu. The --imagespath option contains the path to the directory containing files to add into menu, they will be copied into the boot/ext subdirectory. If this option is not supplied, only BIOS boot images currently existing in boot/ext will be used.

The --force option allows to overwrite existing backup files.

In order for the PXE menu to not be reverted back, posleases2ldap must be stopped, and no pos dump command can be run. Rebooting of the Branch Server should also be avoided for PXE menu to stay intact, since the Branch Server automatically starts the posleases2ldap service.

pos pxe-bootmenu --undo [--force]

Restores the previous default and specific PXE files. The --force option allows to overwrite the current file by backups (for specific PXE, default is always overwritten). The images copied into boot/ext directory are not removed by undo command, should be deleted manually if no more needed.

pos ws-remove [[--workstation]name or MAC[,name or MAC...]|--no-boot-since date|--no-boot-in-last time] [--force] [--dry-run]

Used to delete workstations not booted since specified date (according to scLastBootTime). To delete workstations that were not booted in last T seconds, use: pos ws-remove --no-boot-in-last T. To delete workstations that were not booted since specified date, use: pos ws-remove --no-boot-since date, where date is a date/time string compatible with the Linux date command, for example 2013-08-13 15:21:14.

pos role-mode [--branch] [--enable|--disable|--allow-global|--disallow-global|--status]

Sets role mode. The --branch option specifies the branch on which to act, assuming local branch if not set and run on Branch Server. The --enable option enables the rolebased mode. The --disable option disables the rolebased mode. The --allow-global option allows and the --disallow-global option disallows global roles. The --status option prints the current role mode setting.

pos cfg-md5 [--branch] [--role|--cash-register|--workstation] --cfgname or pos cfg-md5 --dn

Sets configuration md5 sum. The --branch option specifies the branch on which to act, assuming local branch if not set and run on Branch Server. The --role option specifies the local role name or DN to use. The --cash-register option specifies the terminal to use, must be used together with the --role option. The --workstation option specifies the workstation to use. The --cn option specifies the name of scConfigFileTemplate to act on. The --dn option specifies the direct name of scConfigFileTemplate to act on.

The global option --branch scLocation DN specifies the branch for use on the Administration Server.

B.3.13 save_poslogs

The save_poslogs is a tool for collecting log files, configuration files, and LDAP directory content for easier error reporting.

B.3.13.1 Function

The save_poslogs filename command collects all SUSE Linux Enterprise Point of Service relevant configuration files (except salt.key, so that stored passwords remain encrypted), all log files, and the whole LDAP database. It creates an archive containing the collected items and log files with a complete list of collected items. The produced archive is compressed according to filename extension. Recognized extensions are .tar, .tgz, .tar.gz, and .tar.bz2.

B.3.13.2 Usage

The behavior of save_poslogs can be altered by the following options (in any combination):

--noldap

No LDAP database content is collected.

--nolog

No log files are collected.

--noconfig

No configuration files are collected.

B.3.14 posSyncSrvPart

Creates a directory structure for offline boot on the SUSE Linux Enterprise Point of Service service partition.

B.3.14.1 Usage

posSyncSrvPart is started with the following command:

posSyncSrvPart [--server host|path] [--server-type tftp|ftp|local]
    [--source-config config] [--dest-config config]
    [--cleanup] [--dest-dir dir]

The following otions are available:

--source-config

Name of the configuration file on Branch Server. Default: config.mac with fallback to config.default.

--dest-config

Name of the configuration file on the service partition. Default: config.default.

--server

Branch Server host name. The default value is tftp.

--server-type

tftp or ftp or local. The default value is tftp.

--dest-dir

The path to the service partition. Default: /srv/SLEPOS if it is mounted.

--cleanup

Delete all files on service partition that are not referenced from the configuration file.

B.3.15 posAdmin-GUI

posAdmin-GUI is a graphical tool for creating new Branch Server, Image, and CashRegister objects.

B.3.15.1 Usage

posAdmin-GUI is started with the following command:

posAdmin-GUI [YaST2_parameters] [SLEPOS_XML_file]

where YaST2_parameters is the path to the optional SUSE Linux Enterprise Point of Service XML file and YaST2_parameters are optional YaST parameters. The following YaST options can be used with posAdmin-GUI (in any combination):

--fullscreen

Fullscreen mode is used for `opt(`defaultsize) dialogs.

--noborder

No window manager border is used for `opt(`defaultsize) dialogs.

--auto-fonts

Picks fonts automatically, disregarding Qt settings.

--help

Displays YaST help text.

B.3.16 posLDIFReport

The posLDIFReport script generates a report with a list of all Branch Servers and terminals in the SUSE Linux Enterprise Point of Service environment. The report can be limited to terminals booted since a specified date. The report is generated from the LDIF file, which can be obtained suing slapcat or from the save_poslogs TAR archive.

B.3.16.1 Usage

posLDIFReport is started with the following command:

posLDIFReport [-w|--workstations] [-l|--locations] [-s|--statistics] [--since date] [file]

where file is the path to the LDIF file. If the file is not specified, the standard input is used. The following options can be used with posLDIFReport:

--workstations

Create workstations report.

--locations

Create branches/locations report.

--statistics

Create overall statistics report.

--since date

Consider only workstations booted since the specified date.

--help

Displays the help.