Siemens Unix V4.0 Installation guide

Edition April 1999
Advanced Server UNIX V4.0
Overview and Installation

This manual is printed
on paper treated with
chlorine-free bleach.
Comments…Suggestions…Corrections…
The User Documentation Department would like to know your
opiniononthismanual.Yourfeedbackhelpsustooptimizeour
documentation to suit your individual needs.
Fax forms for sending us your comments are included at the
back of the manual.
There you will also find the addresses of the relevant User
Documentation Department.
Copyright and Trademarks
Copyright © Siemens AG 1999.
All rights reserved.
Delivery subject to availability; right of technical modifications reserved.
All hardware and software names used are trademarks of their respective manufacturers
Information in this document is subject to change without notice. Companies, names, and data used in examples
herein are fictitious unless otherwisenoted. No part of this document may be reproduced or transmitted inany form
or by any means, electronic or mechanical, for any purpose, without the express written permission of AT&T and
Siemens AG.
© 1985-1998 AT&T. All rights reserved.
© 1985-1998 Microsoft Corporation. All rights reserved.
AT&T is a registered trademark of AT&T Corporation.
Microsoft, MS, MS-DOS, Windows, and Windows NT either are registered trademarks or trademarks of Microsoft
Corporation in the United States and/or other countries.
Microsoft may have patents or pending patent applications, trademarks, copyrights, or other intellectual property
rights covering subject matter in this document. The furnishing of this document does not give you any license to
these patents, trademarks, copyrights, or other intellectual property rights except as expressly provided in any writ-
ten license agreement from Microsoft.
All other companies and product names are trademarks or registered trademarks of their respective holders.

Product Manual U7613-J-Z815-6-76
© Siemens Nixdorf Informationssysteme AG 1995 Pfad: D:\O7613e6\u7613e.k01
1Preface
Advanced Server for UNIX can be used to integrate personal computers, which are
operated under MS-DOS®(also running MS Windows or MS Windows for Workgroups),
MS®OS/2 or OS/2®(referred to as OS/2 in this manual), Windows 95/98 and MS Windows
NT®operating systems, in local networks (LAN, Local Area Network and WAN, Wide Area
Network). Advanced Server for UNIX allows the operation of various systems in a network.
Advanced Server for UNIX V4.0 (Advanced Server for UNIX in this manual) provides users
with server functions for the local network. It extends UNIX®to a network operating system.
Advanced Server for UNIX corresponds to Windows NT Server. The network server is
based on systems with the operating system UNIX. Cooperation with Microsoft®has
ensured that Advanced Server for UNIX is compatible with Windows NT Server.
The operating system is generally referred to as UNIX in this manual. This term is
used generically to include all UNIX operating systems on which Advanced Server
for UNIX is installed, for example Reliant UNIX.
Advanced Server for UNIX is also used in abbreviated form as AS/X, as well as
sometimes as AS/U or Advanced Server.All of these terms are synonymous for the
same product.
The description of the entire Advanced Server for UNIX product covers several manuals.
The “Concepts and Planning” manual provides information on the structure and function-
ality of Advanced Server for UNIX and describes, among other things, the differences in
comparison to LAN Manager/X.
This manual provides information on the enhancements that are implemented in Advanced
Server for UNIX; it supplements the information in the manual entitled “Concepts and
Planning”. The installation and configuration of Advanced Server for UNIX on the UNIX
system are also described in that manual.
The “API Reference” manual contains information on the API (Application Programming
Interface) with regard to syntax and functions. It is supplemented by online documentation
which is supplied with the package for the manual pages.
The “SNMP Service” manual contains information on the installation and configuration of
an extension for the SNMP agent (Simple Network Management Protocol), which among
other things allows network events to be determined centrally. This manual is part of the
LAN Manager/X V2.2 series of manuals.
i

Preface Target Group
Product Manual U7613-J-Z815-6-76
© Siemens Nixdorf Informationssysteme AG 1995 Pfad: D:\O7613e6\u7613e.k01
The “User's Guide for MS-DOS Clients” and “User's Guide for MS Windows Clients” are
aimed at users of the MS-DOS or Windows clients. They provide information on starting up
and closing down clients, and on shared directories and printers. They also provide refe-
rences to the commands available for working with the client. The manuals “Installation
Guide for Clients”, “MS Network Client V2.2”, and “MS Network Client V3.0” describe how
to install these clients.
The manual “NetWare Connectivity” contains information on how your MS-DOS client can
work simultaneously with Advanced Server for UNIX or LAN Manager servers and with
NetWare®servers. It also contains installation and configuration instructions for NetWare
Connectivity.
1.1 Target group
This manual is intended for the system and network administrator, who is responsible for
installing, configuring, and operating Advanced Server for UNIX.
The network administrator is known as the administrator in this manual.
●The administrator requires the rights of the system administrator root and
must have an in-depth knowledge of the operating system and of the Advanced
Server for UNIX product. The tasks of the administrator and the system admi-
nistrator are undertaken by one person.
●In order to execute administrator commands using the net commands, you
simply need to log on with net logon Administrator <password>.
i

Preface Summary of Contents
Product Manual U7613-J-Z815-6-76
© Siemens Nixdorf Informationssysteme AG 1995 Pfad: D:\O7613e6\u7613e.k01
1.2 Summary of contents
Information that became available after this manual went to print is contained in the
SIreadmeM package which is supplied with Advanced Server for UNIX.
The chapter “Preface” provides users with an overview of the content and structure of this
manual.
The chapter “Introduction to Advanced Server for UNIX” contains information on the supple-
ments and changes which you will require in addition to the information contained in the
“Concepts and Planning” manual.
The chapter “Advanced Server for UNIX architecture” contains an overview of the process
model and of internal and external Advanced Server for UNIX communication.
The chapter “Installing Advanced Server for UNIX” contains information on the hardware
and software requirements of your server system. It also provides instructions for trans-
ferring the Advanced Server for UNIX software onto the server system as well as all the
information required to configure the system and Advanced Server for UNIX software, and
to create a development environment for Advanced Server for UNIX applications.
The chapter “Configuring Advanced Server for UNIX” contains, among other things, the
steps necessary for configuring and for starting NetBIOS and Advanced Server for UNIX.
You should consult the chapter “Administration guidelines” if you want to change the role of
the server, for example if you have installed and configured Advanced Server for UNIX.
Among other things, the chapter also describes how to enable a CD-ROM drive for
Advanced Server for UNIX.
The chapter “Tools for special tasks” describes other tools offered by Advanced Server for
UNIX. These are generally only relevant when used with particular applications.
Another chapter is dedicated to “Installing Network and Administrative Client Software”.
The next chapter is about “Administering Advanced Server at the Command Prompt”.
Then a chapter describes in detail the WINS service: “Implementing WINS”.
The chapter entitled “Troubleshooting” contains guidelines for resolving errors.
The chapter “Advanced Server for UNIX - directories and files” contains an overview of the
most important files and directories of Advanced Server for UNIX.
The following chapters describe in detail “Advanced Server Registry” and the “Lanman.ini
File”.
The “Glossary”, “Abbreviations”, and “Index” chapters are useful as a reference when
reading this manual.
The “Related publications” chapter lists additional useful documentation.
i

Preface Changes since the last version
Product Manual U7613-J-Z815-6-76
© Siemens Nixdorf Informationssysteme AG 1995 Pfad: D:\O7613e6\u7613e.k01
1.3 Changes since the last version of the manual
The documentation has been updated to conform to the software level of Advanced Server
for UNIX V4.0B.
ForalistofdifferencesbetweenAdvanced ServerforUNIXV4.0B and the previonsversion,
please refer to the section “Compatibility” in the chapter “Introduction to Advanced Server
for UNIX”.
1.4 Notational conventions
The following notational conventions are used in this manual:
Convention Usage
Italics in the main body of text denote file, variable, and
program names, as well as commands and
options in continuous text
Bordered Courier indicates extracts from files
Courier denotes system output
Courier semi-bold denotes user input in a sample dialog
indicates a key or key combination
Êindicates tasks to be performed by the user
denotes important information that must be
heeded
denotes a warning that you must heed to avoid
loss of data or serious errors
Key
i
!

Product Manual U7613-J-Z815-6-76
© Siemens Nixdorf Informationssysteme AG 1995 Pfad: D:\O7613e6\u7613e.k02
2 Introduction to Advanced Server for UNIX
This chapter contains supplementary and additional information on Advanced Server for
UNIX that is not contained in the manual entitled “Concepts and Planning”.
The following topics are dealt with:
●Shared resources and services
●Connection management
●Administration
●Application Programming Interface (API)
The section on “Client-server architecture” contains a short description of the client-server
architecture. The section entitled “Shared resources” contains information on which
network resources of Advanced Server for UNIX can be shared.
The section entitled “Services” introduces the services provided by Advanced Server for
UNIX. The section “Connection management” explains the terms “sessions“ as well as
“connection”. This section also provides information on the security concept of Advanced
Server for UNIX. The manual entitled “Concepts and Planning” contains conceptional infor-
mation relating to this topic.
Finally, the section “Administration of Advanced Server for UNIX” provides information on
remote administration.
Information on the programming interface and on compatibility can be found at the end of
this chapter.

Introduction to Advanced Server for UNIX Client-server architecture
Product Manual U7613-J-Z815-6-76
© Siemens Nixdorf Informationssysteme AG 1995 Pfad: D:\O7613e6\u7613e.k02
2.1 Client-server architecture
One or more server systems and several clients (workstations) are connected in a network
(LAN, Local Area Network and WAN, Wide Area Network) with Advanced Server for UNIX.
The server systems provide services and resources in the local network. In contrast, the
clients utilize the services and resources of the server and generally do not provide any
services and resources themselves in the network.
Provided they are authorized, every client can access every server system in the local
network. Advanced Server for UNIX also supports so-called trust relationships between
domains, which permit the user to access resources in other domains.
2.2 Shared resources
The resources provided by a server system for the network are known as shared
resources. Shared resources are protected against unauthorized access (for more
detailed information, see section on “Security concept”).
Advanced Server for UNIX provides users with the following types of resources, which can
be shared by one or more users in the network:
●Shared directory
●Shared printer
●Interprocess communication resource IPC$
●Network-wide administration (Resource ADMIN$)

Introduction to Advanced Server for UNIX Shared resources
Product Manual U7613-J-Z815-6-76
© Siemens Nixdorf Informationssysteme AG 1995 Pfad: D:\O7613e6\u7613e.k02
2.2.1 Names in the network
In the network, servers, domains, clients, users, and resources are assigned unique
names. The following table describes briefly the various types of names in the network.
Name Meaning
System name Name of the UNIX system
Computername, server name Each server and client in a network must have a unique
computername.
A proposed server name is derived from the system
name when it is being installed first (maximum 15
characters).
Username The administrator provides each user in a network with a
unique username for identification.
Users from other domains with which there is a
trust relationship are addressed with <domain
name>\<username>.
Sharename The administrator assigns a unique sharename to each
shared resource on a server.
Network name, UNC name The network name consists of the server’s computer
name and the sharename of one of this server’s
resources. A connection to a resource is established, for
example, with a network name.
Domain name The domain gets a domain name when you install the
primary domain controller. By default, it consists of the
first eleven characters of the system name plus the suffix
.dom (maximum 15 characters).
i

Introduction to Advanced Server for UNIX Shared resources
Product Manual U7613-J-Z815-6-76
© Siemens Nixdorf Informationssysteme AG 1995 Pfad: D:\O7613e6\u7613e.k02
2.2.1.1 System name
Each UNIX system has a unique name in the network, which can be displayed using the
command uname -n and set as the network node name using the SYSADM utility program.
In order to avoid problems, it is strongly recommended that the system names you
assign are unique throughout the network. While the same system name may
appear several times in different DNS domains, even in the same network,
Advanced Server for UNIX uses the system name internally for generating names
which must always be unique.
2.2.1.2 Computername (server name)
Servers and clients must have a unique name in the network, known as the computername.
The computername of a server is also called server name.
A proposed server name is derived from the first 15 characters of the system name when
it is being installed first. The terms computername and server name are used synony-
mously in relation to the server.
It can be changed to any name (with a maximum of fifteen characters) during installation.
The server name is stored automatically in the lanman.ini file on the server. It is part of the
network name and may only be changed after the installation using special utility programs.
For further information please refer to the section entitled “Changing server attributes” in
the chapter entitled “Administration guidelines”.
●The server name consists of up to fifteen characters: letters from a to z,
numbers from 0 to 9 and the special characters -.~!#$%^&()_{}.
●In the previous Version 2.0, the server name for the LAN Manager/X server had
the suffix .serve. Please note that both LAN Manager/X Version 2.2 and
Advanced Server for UNIX up to version 4.0A10 propose the suffix .srv for a first
installation instead.
●Since Advanced Server for UNIX V4.0B, the default server name proposed
during the first installation is built from the system name without an extension.
●In order not to run into problems when upgrading to upcoming NT/AS/X-
versions in the future, all tools requesting a server name during installation or
reconfiguration offer the DNS-compatible host name (‘uname -n‘) as the default
server name. The extension .srv can still be used, but is not recommended and
no longer offered as a default. Installation/configuration scripts now inform the
administrator about DNS-incompatible server names.
!
i
i

Introduction to Advanced Server for UNIX Shared resources
Product Manual U7613-J-Z815-6-76
© Siemens Nixdorf Informationssysteme AG 1995 Pfad: D:\O7613e6\u7613e.k02
2.2.1.3 Username
Every user of a client is assigned a username by the administrator, which is unique
throughout the network. Users are identified by their usernames in the network.
The username consists of three to fifteen characters: letters, numbers, spaces and
special characters without / \ * ’ " ‘!. Use a maximum of eight characters to achieve
unique mapping between UNIX names and Advanced Server for UNIX users. It is
not recommended to use umlauts or characters like the euro symbol in usernames.
2.2.1.4 Sharename
If a resource on a server is shared, it gets a sharename. The sharename identifies the
resource on the server. A sharename for a resource must appear only once on a server,
however the same sharename may be used several times on other servers in the network.
The sharename is part of the network name.
The sharename consists of up to twelve characters: letters (no umlauts), numbers,
and special characters. For MS-DOS clients, the sharename must comply with the
MS-DOS conventions.
Example
The command net share sf1=c:/u1/public is used by the administrator to share the directory
/u1/public as a resource for the network, sf1 is the sharename of this resource.
●The character string c: must always precede the resource pathname when
sharing directories.
2.2.1.5 Network name
A client user sets up a connection to a shared resource using the network name. The
network name of a shared resource consists of the computername of a server and of the
sharename of the resource shared on this server.
Example
The command net use j: \\server1\sf1 is used by the client user to set up a connection to the
shared resource with the sharename sf1, which is located on the server with the
computername server1. The network name of the resource in this case is \\server1\sf1. Using
the command dir \\server1\sf1 or dir j: you can then display the contents of the shared
directory.
i
i
i

Introduction to Advanced Server for UNIX Shared resources
Product Manual U7613-J-Z815-6-76
© Siemens Nixdorf Informationssysteme AG 1995 Pfad: D:\O7613e6\u7613e.k02
2.2.1.6 Domain name
A domain gets its domain name during installation of the primary domain controller. The
backup domain controllers are assigned during installation of a domain. The assignment of
a client to a domain is defined while it is being installed; it can be reconfigured later or, on
some clients, modified temporarily with the net logon command, for example.
The trust relationship concept means that it is easier to manage and use several domains.
(The manual entitled “Concepts and Planning” contains further information relating to this
topic.)
The default domain name consists of the first eleven characters of the system name plus
the suffix .dom, e.g. the domain name of the server server1 would be server1.dom.
The domain name consists of up to fifteen characters: letters from a to z, numbers
from 0 to 9 and the special characters -.~!#$%^&()_{}.
The domain name may only be changed following installation using special utility programs.
Please refer here to the section entitled “Changing server attributes” in the chapter
“Administration guidelines”.
2.2.2 Mapping of file attributes through Advanced Server for UNIX
This section contains information on how Advanced Server for UNIX maps characters and
file attributes between the server and clients.
DOS
The following DOS attributes are mapped on the server by Advanced Server for UNIX:
●r (read only)
●d (directory)
●h (hidden)
●s (system)
●a (archive)
i

Introduction to Advanced Server for UNIX Shared resources
Product Manual U7613-J-Z815-6-76
© Siemens Nixdorf Informationssysteme AG 1995 Pfad: D:\O7613e6\u7613e.k02
The attributes rand dare mapped to the relating UNIX mechanisms. The attributes a, s and
h, as well as any possible combination of these are translated to Advanced Server for UNIX
by means of UNIX group names. The table below, for example, shows how the MS-DOS
file BSP.DAT with the attributes aand hand the MS-DOS file READONLY.BSP with the attri-
butes a, r and hare mapped under UNIX:
OS/2
The extended file attributes of the HPFS (OS/2 extended attributes) contain additional infor-
mation on OS/2 files such as long filenames or comments, for example. The UNIX file
system does not support all attributes, so Advanced Server for UNIX creates a hidden
shadow file for each file with extended attributes. This shadow file has the default name
.EA@<filename>. For example:
The autoexec.bat file has a shadow file with the name [e-mail].
The period (.) as the first character in the filename hides the file under UNIX. The
hidden files are not displayed with the ls command. To do this, use the ls -a
command.
You must try to ensure that these files are only handled under OS/2. If you delete or copy
the files under UNIX, you should also delete or copy the shadow file accordingly.
It is not possible to copy these files with their attributes from an Intel-based to a
RISC-based UNIX system using UNIX commands, as the internal formats do not
match. When the server system is changed, copy the files from the first server to an
OS/2 PC first and from this PC to the other server.
The shadow files of LAN Manager/X 2.2 are compatible with those of Advanced Server for
UNIX and can be continued to be used unchanged.
You should also be aware that with the current version of Advanced Server for UNIX, files
with extended attributes cannot be transferred via the replicator service and also cannot be
copied locally, for example, with lmshell.
Thedefault value of the EAFilePrefix registry parameter has changed since Version 4.0A10
of Advanced Server for UNIX. Instead of .ea@, the value .EA@ is now used to ensure
compatibility with Advanced Server for UNIX V3.5.
Permissions Owner Group Filename
rw-rwsr-- lmxadmin DOS-a-h bsp.dat
r--r-sr-- lmxadmin DOS-a-h readonly.bsp
i
!

Introduction to Advanced Server for UNIX Shared resources
Product Manual U7613-J-Z815-6-76
© Siemens Nixdorf Informationssysteme AG 1995 Pfad: D:\O7613e6\u7613e.k02
Existing configurations are not modified during an upgrade installation. You should
therefore use either the Registry Editor or the regconfig command to set the value of the
EAFilePrefix parameter in the registry to .EA@ under the key
SYSTEM\CurrentControlSet\Services\AdvancedServer
\FileServiceParameters.
If you previously operated Advanced Server for UNIX V4.0A10 with the setting UseEAs=1,
you will now have to rename all hidden shadow files with the extended file attributes.
Use the following command to display all existing shadow files:
find / -type f -name ’.ea@*’ -print
The following shell script can be used to give all old shadow files the new prefix .EA@:
for eafile in ‘find / -type f -name ’.ea@*’ -print‘
do
newfile="‘echo $eafile | sed ’s/\.ea@/.EA@/’‘"
echo rename "$eafile" to "$newfile"
mv "$eafile" "$newfile"
done
Advanced Server for UNIX will only find the extended attributes of a file if the
associated hidden shadow file has the same prefix as is set in the current Advanced
Server for UNIX configuration instance. It would be best to change the file and
directory names and the registry parameters when the server is stopped and then
start the server again.
2.2.3 Share table (list of shared resources)
All shared resources are comprised in the share table. Every resource shared using the
command net share is entered in the share table. Every resource deleted using net share
/delete is removed from the share table.
Advanced Server for UNIX stores the share table in an internal format in the registry. The
share table is loaded automatically each time Advanced Server for UNIX is started. The
various types of shared resources are introduced in the following sections.
!

Introduction to Advanced Server for UNIX Shared resources
Product Manual U7613-J-Z815-6-76
© Siemens Nixdorf Informationssysteme AG 1995 Pfad: D:\O7613e6\u7613e.k02
2.2.4 Shared directory
A shared directory is a file tree of a server system, which was shared for the usage in the
local network. Users can access the shared directory from a client using the sharename.
In this case, users work with the shared directory as they would with a local drive or
directory on their clients.
The security check is not taken into account in the following description in order to
avoid complexity.
The administrator is responsible for assigning a directory (for example with the server
named server1) to a sharename. The administrator links the local directory name
/u1/public1 tothesharenamesf1 usingthecommand:netshare sf1=c:/u1/public1,at the same
time sharing this resource for use in the local network.
●Thedirectorymusthavebeencreated beforehand,otherwise theadministration
interface reports an error.
●The character string c: must always precede the resource pathname on the
Advanced Server for UNIX.
Access information is assigned to shared directories using net perms, which is stored in the
AS/X database (acl).
For example, using net perms c:/u1/public1 /grant group1:fullcontrol the group group1 is
assigned read, write, and execute permissions as well as the permission to create files and
directories, to change or delete attributes and to change the permissions for these direc-
tories.
●UNIX permissions have a higher priority than permissions assigned using net
perms. Thus, for example, the above directory has no write authorization if the
permissions r-x-r-x-r-x are set up using UNIX. If problems arise, the UNIX
permissions can be set temporarily to rwxrwxrwx to establish whether the
missing UNIX permissions have caused the problem.
i
i
i

Introduction to Advanced Server for UNIX Shared resources
Product Manual U7613-J-Z815-6-76
© Siemens Nixdorf Informationssysteme AG 1995 Pfad: D:\O7613e6\u7613e.k02
Authorized users can assign this shared directory to their clients. The network name of the
shared directory (in accordance with DOS naming conventions) \\server1\sf1 is linked on the
client to a local drive letter, e.g. j:, using the command net use j : \\server1\sf1.
The user may have to allow additional drive letters on the client in the configuration
file config.sys using the command lastdrive.
The client user can then access the shared directory using the drive letter j:. All attempts to
access files (copying files and directories, editing files etc.) made by the user on drive letter
j: are mapped on the file system of the server.
The shared directory can therefore be used by a user or a user group. If several users wish
to process a file at the same time, entire files or parts of files can be locked using file locks
for the duration of processing. Read and/or write locks are available.
Older MS-DOS versions or programs are not network-ready, in this case only one
user at a time can access a file.
Advanced Server for UNIX maps the interfaces available under the MS-DOS, OS/2,
Windows, Windows for Workgroups, Windows 95/98 and Windows NT operating systems
to UNIX mechanisms in order to manipulate files and directories.
For further information, please refer to the manual entitled “Concepts and Planning”.
2.2.5 Shared printer resource
As an administrator, it is possible to share the printer queues for the network. The
administrator can also check the status of the printer queue using the corresponding admin-
istration commands and can manipulate the print jobs (delete, for example).
The printout waits in the printer queue and is then printed on a printer connected to the
UNIX system or on a printer connected to a specially configured client (shared client
printer). For further information, please refer to the chapter entitled “Configuring Advanced
Server for UNIX”.
2.2.5.1 Printer spoolers
Interfaces for the following spoolers are available for Advanced Server for UNIX:
●Standard spooler (AT&T®high performance interface)
●SPOOL V4.2 (and above) for all Reliant UNIX systems
Please refertothesection“Configuring printersontheUNIXsystem”forinformationon how
to configure the interface to the spooler.
i
i

Introduction to Advanced Server for UNIX Shared resources
Product Manual U7613-J-Z815-6-76
© Siemens Nixdorf Informationssysteme AG 1995 Pfad: D:\O7613e6\u7613e.k02
2.2.5.2 Shared client printer
It is also possible to route the output of the printer spooler to a printer which is connected
toaclient (sharedclient printer).Forfurtherinformation, pleaserefertothemanuals entitled
“MS Network Client V2.2” and “User's Guide for MS-DOS Clients”.
2.2.5.3 Printer server
The output of the printer spooler can also be routed to server and client systems that can
share a printer resource (e.g. Windows for Workgroups, Windows NT).
2.2.5.4 Sharing a printer
The administrator shares the printer queue on the server (with the computername server1).
For example, you can enable a printer group or class with the sharename sp1 using the
net share sp1 /print command.
For example, the user of the client with the computername cl3 links to a shared printer. To
do this, he/she assigns the network name \\server1\sp1 with lpt1 using the command (in the
MS-DOS naming conventions) net use lpt1: \\server1\sp1. The user can now work on lpt1: for
all print jobs as he/she would on a local printer.
●For Windows NT-Style Printing the sharing of a printer with UNIX commands is
no longer recommended.
For further information, please consult the manual entitled “Concepts and Planning”.
2.2.6 Interprocess communication resource, IPC$
Advanced Server for UNIX can be used to implement distributed applications: Application
processes on the server system exchange data over the network with application
processes on clients. The resource IPC$ enables this communication using LM named
pipes and mailslots.
Special functions also allow the administration of Advanced Server for UNIX using
programs. For additional information please refer to the manual “API Reference” and in the
manual pages for the API, which are supplied with Advanced Server for UNIX. The
following sections contain further information on interprocess communication.
The IPC$ resource is automatically shared.
i
i

Introduction to Advanced Server for UNIX Shared resources
Product Manual U7613-J-Z815-6-76
© Siemens Nixdorf Informationssysteme AG 1995 Pfad: D:\O7613e6\u7613e.k02
2.2.6.1 LM named pipes
Advanced Server for UNIX also provides LM named pipes. They are bidirectional commu-
nication channels for interprocess communication in the network. They differ from UNIX®
named pipes.
The following example describes the basic procedure for setting up and clearing down an
LM named pipe: An application process withroot authorization creates a named pipe on the
server. The client process on the client sets up a connection to the known named pipe over
thelocal network. Both processes canthenexchangedata usingtheLMnamed pipe.When
the data exchange has ended, the LM named pipe is deleted.
Advanced Server for UNIX must be running in order to use LM named pipes.
Example
The root-authorized process on the server server1 creates a LM named pipe with the name
srvp using the function DosMakeNmPipe (“/PIPE/srvp” , &reference,...) and waits using the
function DosConnectNmPipe (reference) for a connection to be set up (_dos_open) to the client
process.
The client process – under MS-DOS, OS/2, Windows, Windows for Workgroups,
Windows NT or Windows 95/98 – opens the named pipe with
_dos_open ("\\\\server1\\PIPE\\srvp",&cfd,...), and data can now be exchanged between the
processes.
The character “\” must always be specified twice in a C program since the first “\” is
interpreted as an escape character.
The connection to the LM named pipe is set up using the resource IPC$. If a client process
on a client wishes to communicate with an application process on the server, this resource
is connected automatically.
If the LM named pipe is to be closed again after the data exchange, the client process clo-
ses this named pipe using _dos_close(cfd).
The server process can then clear down the connection using
DosDisconnectNmPipe(reference) and delete the named pipe using DosClose(reference).
Further information on LM named pipes can be found in the manual “API Reference” and
in the manual pages for the API.
i
i

Introduction to Advanced Server for UNIX Shared resources
Product Manual U7613-J-Z815-6-76
© Siemens Nixdorf Informationssysteme AG 1995 Pfad: D:\O7613e6\u7613e.k02
2.2.6.2 Mailslots
Mailslots are unidirectional communication channels. They are created by an application
process on the server or by a client process on the client. In contrast to LM named pipes,
several processes can write to the same mailslot simultaneously but only the process that
created the mailslot can read from it.
Example
A reading process (on the server server1) creates a mailslot with the name ms. Thisprogram
waits for messages for the mailslot. The writing program sends a message to the network
name of the mailslot //server1/mailslot/ms.
The developer implements this in the program sources for client processes using the API
functions, in compliance with MS-DOS and OS/2 naming conventions:
In the reading program using DosMakeMailslot(\\\\mailslot\\ms, ..) and in the writing program
using DosWriteMailslot(\\\\server1\\mailslot\\ms, ,..).
The following calls are used in the processes on the server:
In the reading program using DosMakeMailslot(//mailslot/ms, ..) and in the writing program
using DosWriteMailslot(//server1/mailslot/ms, ,..).
2.2.7 Using the UNIX operating system from the PC
You can execute UNIX commands from the PC over the netrun service. For further infor-
mation, please consult “Chapter 5 - Enhanced Reference” in the manual “User's Guide for
MS-DOS Clients”.

Introduction to Advanced Server for UNIX Services
Product Manual U7613-J-Z815-6-76
© Siemens Nixdorf Informationssysteme AG 1995 Pfad: D:\O7613e6\u7613e.k02
2.3 Services
The following additional services can be configured in Advanced Server for UNIX:
The following sections briefly explain these services.
2.3.1 Alerter
This service sends alarm messages to certain client users. For example, alarm messages
are initiated if access permissions are violated when using shared resources and if
important limits are exceeded (maximum error rate when accessing networks and hard
disks and maximum number of logon attempts).
2.3.2 Auditing
Important activities in the network are recorded by this service. These include starting and
stopping the server, user sessions and utilization of shared resources by specifying the
username and time. This list can be displayed if required.
Service Comments
Alerter
Auditing
Replicator
Netlogon
Timesource
SNMP Extension Daemon
Netrun
Browser
Windows Internet Naming Service (WINS)
configurable
configurable
configurable
configured when server is installed
configurable
installed and configured with the asxsnmp
package
configurable
configured automatically
configurable