|
|
|
|
|
HELIOS Mac OS X Release Notes |
||||
HELIOS provides very powerful server products and add-ons for prepress customers. These products are very feature rich. First time users will find a good starting point and an overview about what our products can do for them in our product presentation on the HELIOS web site:
Some information about unique HELIOS benefits for file and print services versus Apple services on Mac OS X can be found at:
- Min. 60 MB of free disk space on the Mac OS X partition is required
- Network interface must be installed and active
- Min. 128 MB of memory is required for Mac OS X with HELIOS (256 MB with "Classic" environment)
- Available UFS partition for HELIOS volume data
(see Setting up disk partitions below)- It is required that you reboot the computer after the installation (see page 10). Otherwise the HELIOS software will fail after you log out.
For the installation of the HELIOS software it is recommended to log in as a user with administrative rights. Else you may be asked to authorize again when changing e.g. access rights in the system. Administrative rights can be verified as follows:
In System Preferences > Users click Edit User-, select the Password tab and ensure that Allow user to administer this machine is checked.
Before you can start the installation it is required that one interface is configured for both AppleTalk and TCP/IP. Use the Preferences panel and select Network to configure TCP/IP and AppleTalk in the respective tabs (Fig. 1).
Important: A correct IP number entry must be specified once and then saved in the Router: field of the TCP/IP tab. Otherwise TCP/IP multicasts will not work.
Note: Whenever AppleTalk is not active, starting the HELIOS services (see "HELIOS Services") will automatically enable it on the first network interface "en0".
Insert the HELIOS CD-ROM in the Mac OS X computer and double-click the "HELIOS Network Installer" CD icon, which appears on the desktop.
Then click on the padlock symbol in order to be allowed to make changes (even if you are already logged-in as "root").
You must authorize again to install the software. If you have administrative rights on the machine you can use your name and password in the authentication dialog (Fig. 3).
The HELIOS Installer shows the Introduction window with the Welcome to the HELIOS Installer message (Fig. 4).
During the installation, Go Back lets you jump one step back, e.g. if you need to see the Introduction window again.
Follow the instructions and, if you accept the terms and conditions of the software license agreement, click Agree Otherwise leave the installation program with Disagree.
A destination where to install the HELIOS software to
must be selected. The Select Destination window displays all available volumes (Fig. 6). For the installation of the HELIOS Services software, 100 MB of disk space are required. In the example, the selected volume named
"Mac OS X" has 4.9 GB of disk space available.
Important: If the HELIOS products are not installed on the same disk partition as Mac OS X the HELIOS software will not work!
The next dialog, Installation Type, lets you select whether you want to run an easy or a customized installation.
In the Easy Install window (Fig. 7) click Install for a complete installation. This requires that you have all HELIOS software licenses. Or choose Customize to install only those components of the software which you have a license for.
In the Custom Install window (Fig. 8) mark the components (via checkboxes) of the HELIOS software which you intend to install and click Install. Please note that the HELIOS Base and HELIOS Base Data packages are required and therefore cannot be deselected.
After you have clicked Install you are informed that a restart of the computer is required after the installation.
Then, the Install Software window opens and a status bar informs you about the progress of the software installation. When the installation is done, the Finish Up window appears (Fig. 10) and the software commences a count-down for automatically reboot the computer, starting at 30 seconds.
If there should occur any error during the installation, the Console.log, as described in Error messages and Fig. 33, provides information on what happened.
After the reboot all HELIOS products will be started automatically.
During the installation two applications, "HELIOS Services" and "EtherShare Admin", as well as the folder
"Admin Plug-Ins" are copied into the "Applications" folder on your Mac OS X volume (Fig. 11).
A double-click on the "EtherShare Admin" icon opens the application. A splash-screen appears (Fig. 12) which disappears after a short while, or instantly when you log in to the program.
Holding down the option key during File > Login switches between the HELIOS login dialog (Fig. 13) and the conventional Mac OS X Connect to Server dialog (Fig. 14).
During the installation of EtherShare Admin the users "root" and "demouser" are created. Both of them come without any password, i.e. their AFP-password field is empty. This means a significant lack of security (anybody can log on to the server as user "root" without needing to know the password), and so you should specify a password for "root".
Note: For your own security, provide your user accounts with passwords to prevent them from unauthorized access and abuse!
Log in to EtherShare Admin with User Name: "root" (leave the Password: field empty). Then open Lists > Users, select the "root" entry from the list and double-click it.
Specify a password for "root" in the Password: field and click Save.
On specifying the password, EtherShare Admin prompts for the new password to be entered once again. This ensures that no typing mistakes have been made. After clicking OK the password will be allocated to user "root".
Note: The password field is always shown empty, even if the user has already allocated a password.
Note: By default, the "root" login is disabled on a Mac OS X machine. Once the "root" password is specified with EtherShare Admin, the "root" login is enabled automatically.
Then set passwords for all other existing users, or add new users (passwords set under EtherShare Admin or PCShare Admin are valid for Mac OS X as well).
Important: Note that if a password is modified via Mac OS X tools our additional password file is not changed.
Note: An optional remote user login (telnet/rlogin) needs to be enabled in "/etc/inetd.conf".
To enable a remote "root" user login the "/etc/ttys" file needs to be configured (insecure option)."HELIOS Services" is a GUI application designed for entering HELIOS software licenses, and for easily starting and stopping HELIOS processes.
The HELIOS Services window appears (Fig. 16) providing information on the HELIOS products status when you click Status. In the example shown below there are currently no HELIOS services running.
The field Machine ID: shows the machine ID of your
Apple computer (Fig. 17). In the other field all HELIOS product licenses are displayed, with Product name, Serial Number, and Expiration Date (Note that the entry in the Expiration Date column remains empty if you are running a full license.).
An extra dialog window opens (Fig. 19) which lets you choose the desired product from the pop-up menu Product:, and lets you enter the serial number (Serial: ), the number of Units:, and the Checksum:. As mentioned before, if you are running a full license of the HELIOS products, leave the Expires: field empty. Otherwise, the expiration date of the demo license must be entered in the Expires: field as well.
Note: The EtherShare and PCShare products are licensed for use on a single computer system ("server"). The server has a unique machine identification ("HELIOS MachID") which is provided by a HELIOS USB dongle. The software can only once be licensed for a given USB dongle (MachID). Compare Fig. 17 and 18.
If you do not enter any Activation Key the HELIOS product you have installed will run in a 3-hour demo mode only.
The Messages: box shows the information that HELIOS services are being started. When all available services are running the display shows Done. (Fig. 20).
A click on the Status button then reveals a listing of all HELIOS processes (Fig. 21) and gives information about their name (Service), their Status, their process ID number (PID), date and time of starting (When), and - if a process has been started more than once - the number of Restarts.
"HELIOS Services" has a feature that lets you specify a shutdown message and the time span to shutdown (Fig. 22).
Specify the shutdown message in the Shutdown message: text box. In the Time to shutdown (minutes): field enter the time after which the services should be stopped.
Note: If you specify "0" for the time to shutdown the services will be stopped immediately.
During the installation, the HELIOS software is registered in Mac OS X's "StartupItems" folder for starting automatically at the next OS boot.
Starting all HELIOS processes on the server manually from a remote shell is done via "/usr/local/helios/bin/start-helios".
Important: Due to a problem in the Mac OS X system library, you must not use the command "bin/start-helios" from the local shell on the Mac OS X machine directly. Instead, use the "exechelper" command:
# cd /usr/local/helios
# sbin/exechelper bin/start-heliosStopping all HELIOS processes on the server is done via the command "/usr/local/helios/bin/stop-helios now".
All HELIOS data volumes should be on a UFS disk partition to allow special characters like "umlauts", etc. Via UTF-8 encoding, UFS will be the only supported volume format. HELIOS volumes on HFS will work as well, but without the support of special characters, e.g. "umlauts".
HFS support should be OK for a simple test drive. The real work, however, should only be done on UFS disk partitions.
From the menu bar select Installer and then the item
Open Disk Utility... (Fig. 24).
The Disk Utility window opens and lets you specify the characteristics of the disk you want to partition.
Choose the Partition tab and specify a name for the new partition (or rename it) in the Volume Information section. In the Format pop-up menu select HFS or UFS partition, and specify its desired size in the Size: field. Click OK.
If you have more than one HFS partition on your disk and want to switch one partition to the UNIX File System (UFS) without deleting the data from other HFS partitions, do the following (using the startup disk):
Boot from the Mac OS X CD-ROM, select Installer from the menu bar and then the item Open Disk Utility...
The Disk Utility window (Fig. 25) opens allowing you to specify the characteristics of the disk you want to erase.
Choose the Erase tab, select UNIX File System in the Volume Format pop-up menu, specify a name for the partition (we recommend not to use space characters!) in the Name: field and click Erase.
If you need to have a UFS-partitioned volume e.g. for test purposes, and you do not want to change the partition of an already existing non-UFS volume, you can set up a disk image volume with the desired specifications.
Note: Creating a UFS volume as described here is just a simple workaround since the performance of a volume created in such a way is good but worse than that of a native UFS volume.
Specify a name for the volume image file in the Save as: field, choose a location from the pop-up menu Where:, specify a Volume Name:, the size of the volume and select UNIX File System from the Format: pop-up menu (Fig. 26).
In the example the image file is saved as "TestImage" on the desktop of the Mac OS X host. The volume name has been specified as "Test UFS Volume" with a size of 40 MB. The format of the drive is UFS (UNIX File System).
The disk image file "TestImage.dmg" and the drive
"Test UFS Volume" appear on the desktop (Fig. 27).
Of course you can specify any location for the disk image file. After double-clicking this file the virtual drive will always appear on the desktop.
Start EtherShare Admin and open Lists > Volumes. Then open File > New to configure the volume (Fig. 28).
In the Directory: field enter the volume path, beginning the string with "/Volumes/" (Fig. 29). Specify an AFP Name: and - if required - a Password: and the AFP Charset:.
If you need to make the volume visible to Windows clients as well, activate the Windows visible checkbox, enter the SMB Name: and select the required character set from the SMB Charset: pop-up menu.
A description of the further checkboxes and fields can be found in the chapter "Server preferences" at the end of this book.
After clicking Save the volume is provided in the specified directory path and can be mounted.
By default Mac OS X will not save or report application core dumps. To enable this add the following two lines to the file "/etc/hostconfig" (the administrator should always be able to monitor all problems on a desktop/server system):
This change can only be done as user "root" (or user id=0). The file can be edited as "root" with the simple editor, e.g.:
All core files will be saved to the "/cores" directory. To avoid core files filling up your disk, old core files should be removed from time to time.
Important: In order to make the changes valid you must reboot the computer!
Due to a Darwin kernel problem with the hardware checksum calculation on UDP broadcast packets, the NetBIOS name server of PCShare will not work properly. To make the NetBIOS name server working, UDP checksums are turned off if PCShare is installed. Please read the script
"/usr/local/helios/etc/startstop/40cksum" for more information and a possible alternative. If the problem is fixed in the Darwin kernel, this script can be removed.
Mount the "HELIOS Applications" volume from the
Mac OS X server and open the folder "Documentation".
You can specify a welcome message to output on Macintosh workstations when they log on to EtherShare. There are no preferences to be specified for this feature. Instead, create two text files "login.msg" and "shutdown.msg" with a UNIX editor (or with SimpleText on a Macintosh), and store them in "/usr/local/helios/public/MacOS" (the "MacOS" folder of the Macintosh volume "HELIOS Applications"). The messages will then be used automatically by the File Server during login and shutdown.
Note: If you are running a demo copy of EtherShare on your server you cannot alter the default welcome message.
A maximum of 199 characters will be displayed (excess characters are truncated). If you want to include national accented characters such as "umlauts" in your messages, use SimpleText to write them: since the Umlaut codes are stored here in Macintosh binary format, it is a lot of work to enter the right codes with a UNIX editor.
As a new feature in EtherShare Admin you can specify EtherShare and PCShare server names for the server you are logged-on to.
In EtherShare Admin open Lists > Server Preferences. In the Macintosh Server Name: and Windows Server Name: respectively enter the name with which you want the server to appear in the network to Macintosh and PC clients and click Save. Then restart "HELIOS Services" in order to make the new names available for EtherShare and PCShare clients.
Our software supports the Service Location Protocol (SLP), which allows users under UNIX systems to find available services without any knowledge of host names. Under Mac OS X SLP is preferred over the old AppleTalk Name Binding Protocol (NBP).
User Agents (UA)
This is basically the software that the user or a service uses to register, deregister and find services. Examples for such User Agents are the "slptool", which you can find in
"/usr/local/helios/bin", or the Network Browser under
Mac OS 9.x or Mac OS X.
Service Agents (SA)
An SLP Service Agent is responsible for storing information of services on a single system, answers User Agent calls and informs Directory Agents of local information changes. Examples of such Service Agents are HELIOS SLP-servers on systems with a single network interface, or Mac OS 9.x and Mac OS X clients with activated File Sharing.
Directory Agents (DA)
These agents act as a central repository of a network. It collects the information of Service Agents to build a complete database of the whole network, which can be accessed by User Agents. A HELIOS SLP server on a computer with several network interfaces becomes Directory Agent by default.
Service and Directory Agents are initiated by the same program ("slpsrv"), that can be configured to run as a Service or Directory Agent.
In the absence of a Directory Agent, User Agents that look for services will have to ask for Service Agents. Every Service Agent that sends a reply will then be asked for its local services of a certain kind. If a Directory Agent is available a User Agent will only contact the Directory Agent directly and ask for known services. Therefore Directory Agents can significantly reduce network traffic.
But there is a catch: if a Directory Agent was known, and did not deregister itself, User Agents will always try to contact the Directory Agent directly. If a Directory Agent cannot react (due to a server crash or network problems) they will wait for the connection to time out (which can take several minutes) before they start to look for other Directory or Service Agents.
Another difference between Directory and Service Agents arises on systems with multiple network interfaces. By default "slpsrv" works on such systems as a Directory Agent, so it gathers the services on each connected network, and computers in one network can use services in another network. If you want to configure "slpsrv" to work as a Service Agent, so that computers cannot see services in connected networks, please put an empty text file with the name "slp.conf" into the "var/conf" subdirectory of our product directory (normally "/usr/local/helios") and enter the text "net.slp.isDA = false" into this file.
In the Printer List window click Add Printer- and select LPR Printers using IP (using the HELIOS server TCP/IP address and printer name).
In the Printer List window click Add Printer- and select
LPR printers using IP (using the TCP/IP loopback address "127.0.0.1") from the pop-up menu.
In the Printer List window click Add Printer-, select AppleTalk from the pop-up menu and enter the HELIOS printer queue name.
Open Applications > System Preferences > Sharing and activate Web sharing by clicking the respective button.
Log in as "root" and start Applications > Utilities > Terminal. At the command line enter "cd /usr/local/helios/sbin".
The PDF Internet Printing installation needs to know where the Perl binary is installed on this system.
In the following, the installation script "webinstall" will ask you to accept the default paths for the PDF Internet Printing components. You should confirm each "suggested" path by pressing the ENTER key. However, if you want to use different paths for the installation, which is normally not necessary, specify the new path in the respective line and then press ENTER.
Note: The next two steps, Installing additional ICC-Profiles and Installing additional fonts must only be taken if the installation is carried out from the Internet test-drive. This is because only a limited amount of ICC-Profiles and fonts were included in order to keep the download size of the test-drive small.
In order to install the whole selection of ICC-Profiles, mount the ICC-Profiles volume from an existing HELIOS server (e.g "Sun") and copy all profiles to the Mac OS X volume.
The test-drive includes only the "Standard 14 PS fonts". Additional PS fonts to be used with PDF Handshake and Print Preview can be installed via EtherShare Admin
List > Fonts > New ...
Open Applications > Utilities > Console as shown in Fig. 33.
A very easy way to monitor activities on the Mac OS X server is to do it with the CPU Monitor application:
Open Applications > Utilities > CPU Monitor and, from the Processes menu, select Open Top- (Fig. 34).
Note: Since the Open Top- command keeps the server
up to 20% busy use it only as long as you need it for maintenance purposes.The "Classic" environment is very CPU and memory intensive and therefore we do not recommend to start the "Classic" environment on a Mac OS X machine which is being used as a server.
Note: The "Classic" environment cannot see Mac OS X AppleTalk services from the Mac OS X environment. Printer queues in the Mac OS X environment e.g. will not appear in the classic Chooser. Please use a separate Mac OS 8/9 for working with classic applications on a server volume.
- Login as user "root"
- Launch the Mac OS X Terminal application
- Type the following commands:
# cd /usr/local/helios
# bin/stop-helios now
# sbin/uninstall base
# cd ..
# rm -rf helios
# rm -rf /Library/Receipts/HELIOS*
Mac OS X has a special automatic network configuration which is great for desktops and mobile computers but dangerous for servers. If the network cable is not connected to a switch or hub Mac OS X will not configure the network interface for TCP/IP or AppleTalk. If an active network link goes down (e.g. you disconnect your Ethernet cable for a second) the entire TCP/IP and AppleTalk configuration will be removed. If the link is restored, TCP/IP and AppleTalk will be initialized again.
Boot Mac OS X only if the network cable is connected (HELIOS services will not start if no network interface is configured).
If a network configuration will be changed or the network link is temporally down please issue a "stop-helios now" and "start-helios" or reboot your system which automatically starts all services. You can also use the GUI dialog to stop and restart the HELIOS services. This procedure is described in Fig. 20 under Demo mode.
We have successfully tested all HELIOS server products under Mac OS X. For all tests we used remote clients without working directly on the server machine; no "Classic" environment was used.
If the Mac OS X operating system crashes with a panic error, please write down all messages shown on the server screen and report it to Apple:
Note: Normally all preferences for program functions and behavior of the HELIOS products are set via EtherShare Admin. That means that it is not required to modify preferences manually. Nevertheless, in the following we describe the single preferences and their function.
The server preferences are stored in a binary file. In the following, the preferences are listed by name, type, and default value. The default value is used by the HELIOS services unless another value is specified, e.g. in the EtherShare Admin.
The programs "prefrestore", "prefdump", and "prefvalue" can be used to create and update the preferences file
"/usr/local/helios/var/conf/Preferences".
Setting and retrieving single entries of the preference database can be done using the program "prefvalue" found in "/usr/local/helios/bin".
PreferenceFile is the binary preference database file to use.The default file "/usr/local/helios/var/conf/Preferences" will be taken if omitted. The -r option stands for "recursive delete" and is used together with -d.
Valuefile is the path name of a file to print a preference value to, or read a preference value from. If omitted, "stdout" or "stdin" respectively will be used.
"prefvalue" is the command, -k the key
(here Volumes/public/AFPPublish]), -t the value type (here bool for Boolean), and the last argument is the value to set (here TRUE). In the following, to each preference the type (e.g. bool) and default value (e.g. TRUE) is given.
"PreferencesFile" is the binary preference database file which contains the preferences. If omitted, the default file
"/usr/local/helios/var/conf/Preferences" will be taken.
If "ASCIIPreferenceExport" is specified the preference database will be exported to that file. If omitted, the preference database will be printed to "stdout".
Restoring preferences which have been dumped into a readable text file (e.g. with "prefdump") back into the binary "Preferences" file can be done using "prefrestore".
"PreferencesFile" is the binary preference database file which imports the preferences from "ASCIIPreferenceExport". Any old preferences are deleted with the -c option, otherwise existing files are merged to the preferences.
All of the following preferences are not set by default, meaning they are not listed in "prefdump" output, and HELIOS Services will use the given default values. When a different value is set by means of "prefvalue", this will take precedence. To revert back to the default value, use "prefvalue -k '<key>' -d" to delete the preference entry.
Specifies the AppleTalk (NVE) name of the File Server. This is the name with which it is known to the network.
Specifies the name of the AppleTalk zone to which the file server should be allocated. The chosen zone must be one of the local zones that the server is connected to. You can test this with the "zones -l" command.
The default for this parameter is 10 * sessions, where "sessions" is equal to the number of units (clients) for which you bought your license.
Do not set this preference to an unnecessary high value because this increases HELIOS Services' requirement for UNIX system resources.
Specifies the maximum number of workstations (clients) that are permitted to work on the file server simultaneously. This value should normally be the same as the total number of Macintosh workstations that are connected to the AppleShare server. The value you choose should be less than or equal to the number of sessions allowed by your software license. The maximum tolerable number of workstations depends on the type of Macintosh applications you mostly use (whether they are file-intensive or client-server applications), on the configuration of your Mac OS X system, and on its expansion stage.
This preference specifies the maximum number of files that can be opened by the file server process simultaneously. The achievable maximum cannot exceed the maximum number of open files per process currently allowed by the host. To conserve system resources, do not set this value higher than necessary.
Specifies the user name which is automatically allocated to guest users. The name is invisible to guest users, it is solely used to assign an entry for guests in the user list. If this parameter is specified, the file server automatically supports guest access to available volumes. Otherwise, guest access to available volumes is not possible.
"afpsrv" normally simulates Finder info (such as file type and creator) automatically for files without Macintosh resource. The type of file is determined by inspecting the file's contents. This allows about 20 different icons to be shown for non-Macintosh files.
In the case of files created by MS-DOS applications, the file type is typically indicated by adding a suffix to the file name, the so-called the file name "extension". For example, DOS executable programs have the extension ".COM" or ".EXE" and DOS batch files have the extension ".BAT". Under EtherShare, suitable icons can be displayed for such files by specifying them in the so-called extension mapping table. This is particularly useful in the case of applications such as FrameMaker for Macintosh which are able to directly read documents created by the MS-DOS version without prior conversion. The suffixes parameter allows you to specify the location and name of the extension mapping table.
Specifies the complete path name of the "chpasswd" program, which is used by "afpsrv" to change passwords in the AFP user list. This parameter only needs to be changed if, for administrative reasons, it is necessary to modify EtherShare's default directory system under Mac OS X.
Specifies the maximum number of AppleTalk data packets that are passed from "afpsrv" to workstations through the network during a transaction. The number of packets may need to be limited if the buffer size in the workstations is too small. localwinsize can be varied to optimize the data transfer rate.
Specifies the maximum number of AppleTalk data packets that are passed from workstations to "afpsrv" through the network during a transaction. The number of packets may need to be limited if the buffer size in the UNIX server is too small. remotewinsize can be varied to optimize the data transfer rate.
Specifies the lowest number allowed for user IDs. All users defined in "/usr/local/helios/var/conf/passwd" which have a lower user number than that specified by minuid are not recognized as valid users of EtherShare. This parameter is provided as an additional security feature.
Specifies the highest number allowed for user IDs. All users defined in "/usr/local/helios/var/conf/passwd" which have a higher user number than that specified by maxuid are not recognized as valid users of EtherShare. This parameter is provided as an additional security feature.
"afpsrv" normally simulates Finder info (such as file type and creator) automatically for files without Macintosh resource. The type of file is determined by inspecting the file's contents. This allows about 20 different icons to be shown for non-Macintosh files. Specify binonly if this feature is not required, in which case all non-Macintosh files will be treated as type DATA/UNIX, which means that UNIX text files will then become invisible to most Macintosh text editors.
The AppleShare selection in the Chooser on the Macintosh accepts passwords of any length from 0 byte to max. 8 bytes. Short passwords may represent a security risk. A password of zero length is equivalent to no password. Specify minpwlen as a numeric value between 0 and 8. To improve security, a meaningful minimum value for this parameter is 5.
As a time-saving feature when logging on, the AppleShare selection in the Chooser on the Macintosh lets you save your File Server user name and/or user password on the Macintosh's local hard disk.
To improve security, set this flag to FALSE to disable the saving of user passwords in this way, in which case all users have to enter their password manually each time they log on to EtherShare.
Note: You can still change your File Server password in the Chooser in the normal way (with Change Password).
The File Server caches Finder information in RAM memory to optimize performance. findercache specifies the number of Finder entries to cache, and thus the amount of RAM needed that should be allocated for this purpose. Higher values require more RAM but lead to a File Server speed improvement for some Finder operations.
Note: Each entry requires about 100 bytes of RAM. The cache is used by only one single "afpsrv" (i.e. client) at a time, since it cannot be shared.
This option has been added to "afpsrv" in order to translate any file which is regarded as type "TEXT".
Whenever you modify a Macintosh file, the changes you make do not necessarily affect both the data file and resource file, and in many cases only the data file is changed. "afpsrv" only checks the modification date of the data file when it needs to display date and time information in the Finder. Accordingly, "afpsrv" is designed to always update ("touch") the modification date of the data file, even if only the resource fork has been modified.
However, "afpsrv" does not normally update the modification date of the resource file if only the data fork has been modified. The modification date of the resource file is usually not important, even to incremental backup procedures, and updating it would waste system resources and slow down the File Server somewhat.
Nonetheless, situations may exist where differences between the modification date of the data and resource files can cause difficulties. Such situations are typically those involving automatic data migration to slower external storage.
Specify the filedatesync flag to cause "afpsrv" to always synchronize the modification date of the resource and data files, even if only the data fork has been modified.
This preference specifies the default mode for new directories. The default value given above (0700) specifies the access rights and means that the owner has "Read, Write and Execute" rights for the directory.
In the Mac OS file system only the owner of a folder or volume can permanently change the folder's layout, e.g. sorting order, icons placement and label settings. This feature has been added to allow workgroups, e.g. users who are all members of the same group, to change layout settings or labels according to the organization of their work.
"afpsrv" will return, by default, the number of offsprings (entries in a subdirectory) as 9999 while enumerating a directory. This option can be turned off by using this flag set to FALSE. Then, the AFP-call "GetFileDirParms" on a directory gives the real number of entries.
This feature is especially useful when folders containing many subfolders, which on their part may contain many files, are in use. The Macintosh Finder, or application program, will request information not only on files in the current folder, but in addition on files in subfolders, although this information is currently not used. Therefore, this option may accelerate the opening and displaying of folders with many subfolders.
There are few Macintosh applications which rely on the exact offspring count. For those, disabling of this parameter may be required.
The texttran flag has been added to "afpsrv" in order to turn off the newline translation for all types of text files. texttran set to FALSE will disable line end translation for all files of type "TEXT", without regard to creator.
Specifies the maximum size of AppleShare/IP data packets that are passed via TCP/IP from "afpsrv" to workstations through the network during a transaction.
Specifies the time interval in seconds how often "afpsrv" checks the amount of free space on the server.
Specifies the IP-address the "afpsrv" program offers to the Macintosh clients for logging in via IP-protocol (if this value remains unspecified, i.e. empty, all IP-addresses on the network interface are allowed).
This preference is applied for handling more than one
IP-address, and is given out in a string in which the addresses appear comma-separated.
Specifies the path of the file containing the access list with the IP-addresses which are permitted to log on to "afpsrv".
This parameter lets "afpsrv" append a record to the system messages if, due to the IP-access list, access to one or more users has been denied.
Specifies the time interval in seconds after which "afpsrv" sends a tickle packet to signal that the server is still running.
If specified, the file names of all edited (written, read, saved, etc.) files on the server are recorded and stored sequentially in an "xferlog" file. Use this option with care since it considerably causes load on the server.
Note: Make sure that an empty "xferlog" file exists at the specified location and set file permissions sufficiently so that "owner"/"group" and "others" can write to that file.
Specifies the path of the file containing the IP-access list, and makes the home directory visible to the respective user.
This preference specifies the time in minutes which a user has at his disposal, idling on the File Server before he gets logged-out by "afpsrv".
Is the time in minutes after which the "afpsrv" program gives the user a warning before he is logged-out by the "afpsrv" idletime parameter.
If set to TRUE Mac OS X sends IP-datagrams first to contact other nodes, but the exact behavior depends on the configured queueing discipline. Some high priority levels may require an effective user ID of 0.
While logging on to the SLP server, each process sends enclosed a "lifetime" value. This preference specifies the time (in seconds) after which the SLP server erases the process from its list, even if it is not running anymore.
Note: This preference is valid on Linux platforms only!
While logging on to the SLP server, each process sends enclosed a "lifetime" value. This preference specifies the time (in seconds) after which the SLP server erases the process from its list, even if it is not running anymore.
While logging on to the SLP server, each process sends enclosed a "lifetime" value. This preference specifies the time (in seconds) after which the SLP server erases the process from its list, even if it is not running anymore.
Specifies the maximum number of network volumes that can be opened by Macintosh users on the File Server simultaneously.
The default is 128 volumes. Each open volume is only counted once, even if it has been opened by more than one user. The absolute maximum value is 450, but the achievable maximum may be limited by the maximum number of open files for the "desksrv" process allowed by the host. This limit is normally set by "desksrv" for itself automatically. In case of problems, refer to "limit" and "ulimit" in your UNIX documentation for details about how to increase the limit manually for your host.
This preference is the AppleTalk type of the Mail Server. This is the type with which it is known to the network. type should normally be set to "MailServer".
This preference sets the AppleTalk (NVE) name of the Mail Server. This is the name with which it is known to the network. Several names in a row, separated by a comma, are optional.
Specifies the name of the AppleTalk zone to which the Mail Server should be allocated. The chosen zone must be one of the local zones that the host is connected to. You can test this with the "zones -l" program.
Specifies the direcory path of which all incoming mail is spooled. Outgoing mail is not spooled, since it is passed directly to the UNIX mail system.
Gives the interval in seconds with which the mail directory is polled for new mail. Usually, you use the "biff" program for mail notification instead, since you get immediate notification this way, and because "biff" needs less system overhead.
The Mail Server only polls for mail at the time interval specified by mailinterval if "biff" has been disabled or is not available for some reason.
This preference is a string containing the official name (UNIX mail name) of your host. This is the name which users of other systems need to include in their mail address when they want to reach you. It is made up of a name (e.g. the host name "osiris") and the domain in which the host resides (e.g. "helios.de").
Specifies the name and path of a file containing a list of
e-mail addresses. The list can be accessed by and maintained from HELIOS Mail. You can use it to save time when you often mail to the same people.
Is the name and path of the UNIX program used to send mail. You should normally use the "sendmail" program for this purpose. In some cases, you may need to use
"/usr/bin/mail" instead. However, you may encounter problems with the mail program, such as lack of 8-bit transparency. You need 8-bit transparency if you want to send mail containing national accented characters such as "umlauts". A character conversion table in the Mail Server allows you to send mail containing "umlauts" to UNIX users, too.
This switch specifies whether or not to use the UNIX "biff" program for mail notification. "biff" is the preferred method, since it needs less system overhead than polling for mail. However, on some systems "biff" is already used by other programs such as "comsat", and may not be available for use by the Mail Server. In this case, the Mail Server automatically falls back to polling for mail.
If you want to release "biff" from "comsat" for use with
the Mail Server, bracket out the corresponding line in the UNIX configuration file "/etc/inetd.conf" by inserting a
"#" at the start of the line.
Then re-initialize "inetd" with the command "kill -1 xxx", where "xxx" is the process id of the "inetd" process. Finally, stop and restart the AppleTalk network with
"stop-helios" followed by "start-helios".
History: "Biff" was the name of a dog belonging to a Berkeley programmer who wrote part of the UNIX mail system. Biff used to bark each time the postman delivered a (conventional paper) letter to the door.
When you installed the HELIOS software, a new address book was automatically created as the empty UNIX text file "addressbook" in "/usr/local/helios/var/conf". You can add new addresses to the list with the New Address... function of HELIOS Mail. When you use the address book, normally you will also see all users of your UNIX host, including root, in addition to users you have included manually with the New Address... function. Specify FALSE to turn off this feature, in which case the address book will only show users who have been included manually.
If you check Save name in the HELIOS Mail login window, HELIOS Mail makes a note of your name, and the zone and name of the Mail Server you want to use. Next time you start HELIOS Mail, you only need to enter your password. Furthermore, if you log on first to the EtherShare File Server on the same host, you will not have to enter your name and password for either the Mail Server or the "Mail Notification Feature" anymore. This is convenient, but presents a security risk if you leave your Macintosh unattended with volumes mounted - even if you have quit HELIOS Mail, others can start it again and have access to your mailbox without needing to type in any password. Specify FALSE to force HELIOS Mail to ask for a password each time it is started. This is similar to unchecking the Save name box in the HELIOS Mail login window, but applies to all HELIOS Mail users on that host. In this case do not forget to always uncheck Save password in the same window.
Specifies the maximum number of data packets that are passed from "mailsrv" to workstations through the network during a transaction. The number of packets may need to be limited if the buffer size in the workstations is too small. This flag can be varied to optimize the data transfer rate.
Specifies the maximum number of data packets that are passed from workstations to "mailsrv" through the network during a transaction. The number of packets may need to be limited if the buffer size in the UNIX host is too small. This flag can be varied to optimize the data transfer rate.
Specifies the path of the UNIX vacation program. It is required if you want to make use of HELIOS Mail's vacation message option. For details about the vacation program and the ".vacation.msg" file, see the respective UNIX man pages.
While logging on to the SLP server, each process sends enclosed a "lifetime" value. This preference specifies the time after which the SLP server erases the process from its list, even if it is not running anymore.
This preference sets the AppleTalk (NVE) name of the PAP-Server. This is the name with which it is known to the network. Several names in a row, separated by a comma, are optional.
This preference is the AppleTalk type of the PAP-Server with which it is known to the network. This preference should normally be set to "LaserWriter", "ImageWriter" etc., since only then it will be recognized by the standard Macintosh Chooser extensions on the workstations. If the workstations are provided with a later version of the LaserWriter program, which also allows other printer types, a different type can be specified here if necessary.
Specifies the name of the AppleTalk zone to which the PAP-Server should be allocated. Thus it determines the zone in which the Print Server can be seen in the Chooser. The chosen zone must be one of the local zones that the server is connected to. We strongly recommend to test this using the UNIX program "zones -l".
Specifies the path (including the file name) of an alternative "lpr" program to the one normally used by "papsrv". The lpr parameter can be used to specify another "lpr" program which is different from the one normally selected by "papsrv". You should use this parameter if you have developed your own custom "lpr" program. You can also use this option to specify a shell script.
Specifies the path (including file name) of a custom filter program which is called in a pipe with the "standard input" connected to the print job and the "standard output" connected to "lpr". The job will already be resolved if the resolve switch is specified.
The "filtercmd" program can then process the file (which is not resolved) as required. The output file should appear under the same name ("spoolfile") given in the argument - "papsrv" will wait until the custom filter program has finished before processing the job further. Compared to the filter parameter, filtercmd can be used for example to add a header (e.g. a PostScript init) or a trailer to the file without having to process the whole file. Use filter instead if you need to parse the entire file, e.g. for font names or job information.
The resolve switch causes "papsrv" to "resolve" all print jobs for the specified printer queue before they are sent to "lpr", i.e. "papsrv" incorporates all required font, dictionary groups and OPI image information into the jobs in advance, and resolves "%%Include..." references. This is needed whenever you want to use printers that cannot be driven directly by the printer interface programs supplied with EtherShare. But be aware that if you use the resolve switch you will need substantially more spooling space on the local server.
Normally, print job resolving is done on-the-fly, by the specified interface program, such as "papif", and jobs queued in the printer's spool directory are not yet resolved. This design approach saves spooling storage, particularly if you are using EtherShare OPI.
The resolve switch causes the "papsrv" to call the pseudointerface program "/usr/local/helios/bin/psresolve", which compares the fonts needed by the document with the printer's resident font list ("FONTS" file in the printer's spool directory), and with the list of available server fonts in "/usr/local/helios/var/spool/psfonts/FontDirectory". Thus, this is more intelligent than choosing Postscript Job from the application's print dialog - the latter always includes all document fonts, regardless if needed or not.
You should use the resolve switch to prepare print job files for printing offline or with a printer or typesetter whose hardware interface is not supported by EtherShare, but you must not use resolve in conjunction with the standard EtherShare interface programs, because all references will be included twice and the job will fail.
Be aware that if the job then gets printed on a different host and/or printer, it will not contain all required fonts if it has been resolved with an inappropriate "FONTS" file.
The "papsrv" induces Apple's LaserWriter printer driver to spool the jobs directly to the selected EtherShare queue by default.
This switch determines whether printing to a LaserWriter queue is password-protected or not. In case the flag is set to TRUE, user name and password have to be entered before printing. This setting affects all LaserWriter printer queues on the same server.
entity is the NVE name:type@zone of the printer (e.g. printer1:LaserWriter@HELIOS) with which it is known
to the AppleTalk network. This name is not the same as the AppleTalk name of the printer queue. Note that if print jobs are sent from workstations directly to the printer, they bypass the printer queue, and thus do not gain the advantages of spooling, "prep" file management, etc.
Specifies if the particular printer is published for PAP clients, i.e. for Macintosh clients. The setting reflects that
of the checkbox Macintosh - PAP in EtherShare Admin's Printers: configuration window.
This preference specifies the AppleTalk type of the Terminal Server. This is the type with which it is known to the network. type should normally be set to "UNIXTerminal". The same type must be set in the "Connection Settings" window of the HELIOS Terminal program.
name specifies the AppleTalk (NVE) name of the Terminal Server. This is the name with which it is known to the network. Several names in a row, separated by a comma, are optional.
Specifies the name of the AppleTalk zone to which the Terminal Server should be allocated. This parameter determines the zone in which the Terminal Server can be seen in the Chooser of the HELIOS Terminal program. The chosen zone must be one of the local zones that the host is connected to. You can test this with the "zones -l" program.
This preference specifies a string which is output to each Macintosh terminal whenever a connection is made and before the login itself is started. For example, you can use this parameter to output a company trademark.
Specifies the name of the terminal emulation. This name
is written by "termsrv" to the UNIX environment variable "$TERM" on starting a new connection. In the standard UNIX configuration, the VT100 emulation (i.e. a definition of terminal control codes) is defined in each of the files "termcap" and "terminfo". If you change term to specify another emulation, you must ensure that the new emulation definition has been added to both files. Whereas many programs refer to the "termcap" file, an entry is also required in "terminfo", since, under Solaris 2, some programs refer to "terminfo" (like the editor program vi) instead of "termcap". Note that the standard UNIX VT100 emulation is a subset of the VT320 emulation provided in HELIOS Terminal.
Specifies the maximum number of data packets that are passed from "termsrv" to workstations through the network during a transaction. The number of packets may need to be limited if the buffer size in the workstations is too small. The value of localwinsize can be varied to optimize the data transfer rate.
Specifies the maximum number of data packets that are passed from workstations to "termsrv" through the network during a transaction. The number of packets may need to be limited if the buffer size in the UNIX host is too small. The value of remotewinsize can be varied to optimize the data transfer rate.
This preference sets the AppleTalk (NVE) name of the Admin Server. This is the name with which it is known to the network. Several names in a row, separated by a comma, are optional.
Specifies the name of the AppleTalk zone to which the Admin Server should be allocated. The chosen zone must be one of the local zones that the host is connected to. You can test this with the "zones -l" program.
Specifies the maximum number of workstations (clients) that are permitted to work on the Admin Server simultaneously. This value can be the same as the total number of workstations that are connected to the AppleTalk network, but is usually smaller than that.
Specifies the name and path of the file in which the user, optional AFP user and group data for the NIS ("Yellow Pages") system are stored.
This flag - if set to TRUE - is specified to protect (lock) all configuration data. Then, merely maintaining spool queues is possible.
Specifies the path of the host directory which contains the server font list "FontDirectory". The fonts themselves are contained in the file's subdirectories, arranged alphabetically.
EtherShare Admin allows users with sufficient permissions to configure the EtherShare system from any Macintosh workstation on the AppleTalk network in a convenient and secure way. For example, it can be used to set up users, groups, volumes, and printers, and re-schedule print jobs. Normally, only the system administrator is allowed to make any changes. Non-privileged users can inspect the configuration and the print job queue, but cannot change anything except delete their own print jobs.
Members of the special "system administrators" group can also use EtherShare Admin to make any changes they like, including printer configuration, and sending AFP messages with Lists/Active Users/Message/Message To All... to all AppleShare users logged-on to the EtherShare server. However, these group members are not allowed to modify any information on users with an ID less than 100 (Note that the system administrator has a user ID of 0). The sysadmgroup parameter specifies the name of the special "system administrators" group.
Members of the special "printer administrators" group
can use EtherShare Admin to manipulate print jobs from
a Macintosh workstation, i.e. they are allowed to:
Members of the special "queue administrators" group can use EtherShare Admin to manipulate print jobs and queue configurations from a Macintosh workstation. Thus, they have even more privileges than members of the "printer administrators" group that is described above. Queue administrators are allowed to:
As a time-saving feature when logging on, the AppleShare selection in the Macintosh Chooser lets you save your File Server user name and/or user password on the Macintosh's local hard disk.
To improve security, specify the flag to disable the saving of user passwords in this way, in which case all users have to enter their password manually each time they log on to EtherShare Admin.
Specifies the path of the file containing the access list with the IP-addresses which are permitted to log on to "admsrv".
This parameter lets "admsrv" append a record to the system messages if, due to the IP-access list, access to one or more users has been denied.
While logging on to the SLP server, each process sends enclosed a "lifetime" value. This preference specifies the time after which the SLP server erases the process from its list, even if it is not running anymore.
Sets the Macintosh AFP volume name. The setting reflects that of the AFP Name: field in EtherShare Admin's Volumes: configuration window.
Sets the PCShare SMB volume name. The setting reflects that of the SMB Name: field in EtherShare Admin's Volumes: configuration window.
Specifies the volume password (currently only supported on Mac). The setting reflects that of the Password: field in EtherShare Admin's Volumes: configuration window.
Only set this flag to TRUE for removable media attached to the Mac OS X host which are normally changed while the host is running (e.g. MO drives). Do not apply this setting for local volumes. The setting reflects that of the checkbox Exchangeable in EtherShare Admin's Volumes: configuration window.
This flag must be set to TRUE when the underlying physical media is write protected (e.g. CD-ROM). Then, there is - for all users - only read access to the specific volume. The setting reflects that of the checkbox Read Only in EtherShare Admin's Volumes: configuration window.
This preference specifies how the server handles record locking between clients and UNIX applications.
With this flag set to TRUE, the particular volume is published for Macintosh clients. The setting reflects that of the checkbox Macintosh visible in EtherShare Admin's Volumes: configuration window.
With this flag set to TRUE, the particular volume is published for PC clients. The setting reflects that of the checkbox Windows visible in EtherShare Admin's Volumes: configuration window.
Specifies the user name which is automatically allocated to guest users. The name is invisible to guest users, it is solely used to assign an entry for guests in the user list. The setting reflects that of the checkbox Guest Access in EtherShare Admin's Volumes: configuration window.
The default for guest is "nobody". The specified guest user must exist on your host. The installation automatically creates the user "nobody" if it does not already exist.
This flag makes the host use the Unicode character set encoding on the specific volume. This provides a correct cross-platform file name transfer (particularly if the names contain special characters, such as "umlauts" between Macintosh clients, PC clients, and UNIX servers. The setting reflects that of the checkbox Unicode/UTF-8 in EtherShare Admin's Volumes: configuration window.
This option has been added to the HELIOS server products in order to hide files starting with a dot ("."). The setting reflects that of the checkbox Hide "dot files" in EtherShare Admin's Volumes: configuration window.
This flag specifies how the file server reacts to a file close command from the PC client. close disables the file descriptor caching, so files are closed immediately as soon as the file close command is received. The setting reflects that of the checkbox Close Option in EtherShare Admin's Volumes: configuration window.
Specifies a list of groups which are allowed access to this particular volume. The setting reflects the entries in the Groups: field in EtherShare Admin's Volumes: configuration window.
Specifies the file name of the IP access list that makes the particular volume visible for clients which have one of the IP numbers on the IP access list.
If the UTF8 flag is set the charset flag is used to translate and encode file names to the "MacRoman" or "SJIS" character set. The setting reflects that of the AFP Charset: pop-up menu in EtherShare Admin's Volumes: configuration window.
If the UTF8 flag is set the charset flag is used to translate and encode file names to the "PC850" or "SJIS" character set. The setting reflects that of the SMB Charset: pop-up menu in EtherShare Admin's Volumes: configuration window.
This flag specifies how the file server reacts to a directory close command from the client. closedirs disables the directory descriptor caching, so directories are closed immediately as soon as the directory close command is received.
This flag specifies whether or not the server allows record locking between multiple PCShare clients.
This flag specifies how the server reacts if a PC opens a file for reading or writing without indicating how (and whether) the file can be simultaneously opened by other programs.
Normally, if a file is opened for reading, other users can only open the file for reading ("deny other write"). Furthermore if a file is opened for reading and writing, other users cannot open the file at all ("deny other all").
Specifies the printer connection type for a particular printer, e.g. AppleTalk, TCP, Create PDF, Windows Printer, etc. The setting reflects that of the Connection: field in EtherShare Admin's Printers: configuration window.
Specifies a list of groups, separated by a comma.
A particular printer will only be visible to members of the group(s) which are part of this list.
Specifies the path of the host directory which contains the server font list "FontDirectory". The fonts themselves are contained in subdirectories of the file, arranged alphabetically.
Specifies the path containing PostScript dictionaries and printer "prep" files, such as "AppleDict...", "LinoDict..." and "HeliosDict...". You can specify an alternative path here if one of your printers is not fully compatible to the Apple LaserWriter and needs other dictionaries and/or "prep" files. Normally, all PostScript printers share the same files.
Determines whether printer errors are reported back to the originator of the print job through HELIOS Mail. Even if you specify FALSE, printer errors are still recorded in the printer log file, and many types of errors are also written to the system messages file, allowing you to view them later with EtherShare Admin or an editor program such as vi.
Specifies the time interval in seconds with which the printer interface program interrogates the printer's status channel. As a diagnostic aid, you can use the UNIX "lpq" program to check the status of each spooled printer. "lpq" returns the status messages that you normally see in the dialog box of the LaserWriter driver for locally connected AppleTalk printers.
The Print Server does not return such status messages to the workstations - it only returns them to the "Print jobs" window in EtherShare Admin. The watchtime parameter has been provided because the PostScript processors of some printers time out in certain unusual situations if you check the printer's status channel for extended periods of time.
This switch causes the printer's page count to include the number of banner pages - if, in EtherShare Admin's Settings menu, Banner Page is ticked - in the total amount of pages.
This preference determines that the banner page is ouput after the print job has been terminated on the printer.
PostScript printers normally cannot accept print jobs consisting of "flat" ASCII data. They require the print job to be in PostScript format. ASCII print data can be manually converted to PostScript with the "pstext" utility. In addition to this, the interface programs of the Print Server are also able to automatically detect whether a particular job is in PostScript or ASCII format, by scanning the start of the job for the "signature" string "%!PS-Adobe". If this string is missing, the job is assumed to be non-PostScript, and is converted to PostScript automatically before printing.
This flag determines whether the "Ctrl-D" character should be used to indicate "end-of-print-job". This is necessary if the printer is connected to TCP/IP through a terminal server and a serial interface.
This flag determines whether printer status messages are reported to the AFP-client (or PCShare client, respectively). These messages pop up as display messages and report e.g. paper jams, misfed paper, and other printer-related errors.
This flag determines whether a spooled print job is "marked" with the information that it has already been spooled. If is set to TRUE, a spooled print job is not recognized as already spooled, thus setting this preference to TRUE is only meaningful for the first spooler in line of a chained EtherShare queue.
The parameter ignoreresolveopts, when set, makes a second EtherShare spooler ignore all remarks on resolved references from a prior spooling process. If you merely want a spooler to ignore single references, e.g. references regarding included fonts etc., you may set one or more of the following flags:
With the ignoreprocsetresolveopt flag set, the next (second) EtherShare spooler ignores information about included procsets only.
With the ignorefontresolveopt flag set, the next (second) EtherShare spooler ignores information about included fonts only.
With the ignoreincluderesolveopt flag set, the next (second) EtherShare spooler ignores information about included EPSF files only.
With the ignoreopiresolveopt flag set, the next (second) EtherShare spooler ignores information about resolved OPI-references only.
The preference rsslimit (resident set size limit) is determined by the maximum number of kB a printer interface program can utilize as memory. If this parameter is not set, the memory administration is up to your system settings.
The priority of a printer interface program - compared to other executable programs on the Print Server - can be altered. The UNIX parameter nice lets you increase/reduce the priority, and therefore the speed of a program. The higher the priority of a program, the less "nice" its behavior towards other applications. The values are as follows:
The printer log files ("printer.acct.x") contain information about printing time/date, document name, user, fonts, and more. With this flag set to TRUE, the range of information for each print job is increased by e.g. an OPI image replacement list and the total number of bytes printed.
facility is a string that ought to be set by the system administrator only, since its use requires advanced knowledge on UNIX programming. For further reference see the UNIX manual pages "syslogd(1)".
Specifies the maximum number of data packets that are passed from "papif" to the printer through the network during a transaction. The number of packets may need to be limited if the buffer size in the printer is too small. This preference can be varied to optimize the data transfer rate.
Specifies the maximum number of data packets that are passed from the printer to "papif" through the network during a transaction. The number of packets may need to be limited if the buffer size in the UNIX host is too small. This preference can be varied to optimize the data transfer rate.
Specifies the Internet number of the printer in the TCP/IP network (or of the printer's terminal server, if any).
This preference specifies the service port number (also called the service code), which specifies the process within host which is responsible for the printer. The port number is between 1 and 65535.
Specifies the name of the remote printer on the remote host, as stated in the "/usr/local/helios/var/conf/printcap" file.
When a print job is processed, and the flag is set to FALSE, the print job remains "untouched" and is passed on without any changes.
Specifies whether a separate communications channel for status messages with the address <port+1> is provided.
Specifies the path (including file name) of the Shared Memory "key" file. The file must already exist. The RIP must be configured with the same path.
The RIP and the "Shared Memory" interface program use the key file's "inode" to create a unique numeric key, and do not modify or write to the file in any other way. Accordingly, any existing file (such as "/bin/ls") can be used for this purpose. See the description of "ftok" in your UNIX documentation for related information.
Specifies if any resolving is done within a PostScript job. When a print job is processed to a "Print To Disk" queue, and the switch is set to FALSE, the print job remains "untouched" and is passed on without any changes.
This flag determines whether the suffix ".ps" is appended to the processed print job file. In case the switch is set to FALSE the file name extension ".ps" is omitted.
Specifies whether files which come from a specific printer queue are "marked" with a prefix before their original file name. This may be quite reasonable when several
"Print To Disk" queues print to the same destination.
Specifies the (absolute) UNIX path of the directory, where the processed print job is stored. The file name results from the print job title with the typically appended suffix ".ps".
If dir points to UNIX FIFO (named "pipe") rather than pointing to a directory, the processed print data are written to that "pipe" directly.
If dir starts with a pipe character ("|") the whole string following "|" is recognized as a UNIX command line, and the processed print data are piped into the executed program.
This parameter will only be recognized if dir is specified as well. Specifies the (absolute) UNIX path of the program which, as soon as "diskif" has successfully resolved the print job, is started with the parameters:
HELIOS_JOBSIZE=
<expected print job size (in bytes). The stated value is often smaller than the actual size>
Determines the compression type. You can choose from different types of compressing: LZW and ZIP. None means that there is no file compression applied at all.
Determines the time a processed print job remains on a hold/error queue. If jobholdtime is set to 0, the print job perpetually remains on the hold/error queue. This parameter is compulsory, i.e. it has to be set with a certain value.
A string which contains, separated by commas and without any spaces, the logical (UNIX) printer names of those devices which form a printer group for balancing print loads.
This parameter will only be recognized if distilldir is specified as well. With "string", you can define a file name prefix for all PDF files that are sent to the selected directory. This can help you classify your PDF files if you have several "Create PDF" queues and save all PDF files into the same directory.
This preference specifies the path of the directory to which the UNIX Distiller saves the created PDF files.
This parameter will only be recognized if distilldir is specified as well. With this preference the path of the "distillnotify" program is specified:
HELIOS_JOBSIZE=
<expected print job size (in bytes). The stated value is often smaller than the actual size>
Specifies if any resolving is done within a PostScript job. When a print job is processed to a "Create PDF" queue, and the switch is set to FALSE, the print job remains "untouched" and is passed on without any changes.
If set to TRUE, this preference determins that the PDF page size is taken automatically from the BoundingBox if the job is an EPSF file rather than a PostScript file. This preference is only meaningful if distillresolve is set to TRUE as well.
If a file is sent to a preview queue, with this option set to FALSE, the print job remains "untouched" and is processed without any changes.
This parameter will only be recognized if pdfdir is specified as well. With "string", you can define a file name prefix for all preview files that are sent to the selected directory. This can help you classify your previews if you have several preview queues and save all preview files into the same directory.
This parameter may be used to save new preview files automatically into an already created "pdfdir" directory on the server. The value for this preference must be a full UNIX path name, e.g. pdfdir="/helios/views". The EtherShare Admin option Suppress Forward to Hold Queue (or the wait parameter, respectively) will be ignored if pdfdir is specified. The hold queue contains a symbolic link to the preview file in the "pdfdir" directory.
Note: If the print job is renamed or removed from its original location the link does not work anymore and an error message may appear.
Note: Preview files that are saved into a UNIX directory (using the pdfdir parameter) will automatically be assigned a file name extension, namely ".pdf".
This parameter will only be recognized if pdfdir is specified as well. pdfnotifyprog lets you enter the path that leads to a UNIX program. This program will be started automatically after printing has been finished successfully.
HELIOS_JOBSIZE=
<expected print job size (in bytes). The stated value is often smaller than the actual size>
Allowed strings for defining the compression of preview files are "none", "zip", and "jpeg". "none" is the default. "zip" is best-suited, because it guarantees lossless compression. "jpeg" stands for JPEG (quality of compression depends on jpegquality, see below).
This parameter controls whether or not the composite view of your document is included in the preview file.
This parameter lets you decide whether or not you want to have previews of the separation plates of your document.
This preference will induce Print Preview to keep the preview file in the preview queue instead of forwarding it to a hold queue. Set this preference to FALSE if you want to activate automatic forwarding of print jobs.
This parameter controls whether or not smoothing of contours should be applied to the preview files. It should only be switched to FALSE if you intend to print the preview files again, e.g. send them to a printer.
Other than Acrobat Exchange, the Reader software is not able to create thumbnails on its own. Therefore, Print Preview generates thumbnails of all pages you have printed to allow you to make use of the View - Thumbnails and Page option in Acrobat Reader when you check the preview files.
This preferenec lets you specify the resolution you want to have for your preview files. The default is 72 which is the standard monitor resolution. You may enter a higher value if you intend to print the preview files again, e.g. send them to a printer.
This parameter controls Print Preview's virtual RIP memory. The default value is 10 MB. You should use the parameter to enter a value higher than 10 MB - smaller values are not recommended. To guarantee minimum performance of Print Preview, never define less than 5 MB.
This parameter controls Print Preview's global virtual RIP memory. The default value is 2.5 MB. You should use the parameter to enter a value higher than 2.5 MB - smaller values are not recommended. To guarantee minimum performance of Print Preview, never define less than 1 MB.
Usually, PostScript errors - if there are any - are added to the log file. You can switch off the recording of PostScript errors by setting the flag to FALSE.
Print Preview uses for PostScript interpretation the PostScript level that is stated in the queue's PPD file. In case no PPD file has been assigned, the default language level is Level 1. If this parameter is set to FALSE it induces Print Preview to ignore the PPD file entry and to use the default PostScript Level 1.
By default, Print Preview generates an info page for each job on a preview queue and adds it to the preview file. Set this parameter to FALSE to switch off the insertion of the info page.
With this option, you can force Print Preview to use a specific PostScript language level. Possible values are "1" and "2". If you set a languagelevel, this will override the PPD file setting, and the option ppdlanguagelevel - if it is specified at all - will be ignored as well.
This parameter lets you specify the JPEG compression quality of preview files in a range from 0-100.
Specifies the Acrobat compatibility of the created PDF file. If set to 4, the ICC-Profiles specified in EtherShare Admin are integrated into the PDF file and used in so-called
ICC-based color spaces.
A preview queue can be regarded as an RGB or CMYK PostScript device. When rendering a job on a preview queue, a so-called "Color Rendering Dictionary" (CRD) is required for the transformation of PostScript CIE-based colors in a job. Two CRDs are initialized by default - one for the transformation of CIE-based colors into RGB and one for the transformation into CMYK. The RGB CRD corresponds to EBU-RGB, the CMYK CRD corresponds to Euroscale CMYK. The swopcrd flag can be used to change the CMYK standard and select SWOP instead of Euroscale. Particularly American customers should set this flag.
With this preference a list of so-called "time spec" strings for a time queue can be defined. This type of printer queue immediately forwards the jobs to the hold queue during the specified date/time. Outside the defined times the jobs remain in the time queue until the next date/time specification is reached.
[!]Duration/StartTime[,StartTime...][/DayOfWeek[,-DayOfWeek...]
||DayOfMonth[,-DayOfMonth...][/Month[,-Month...]]]
An "!" character (exclamation mark) before the following specifications negates the entry, i.e. date/time in which the time queue must not forward jobs to the hold queue.
In the above given example, print jobs are immediately forwarded to the hold queue on Tuesdays, Wednesdays, Saturdays and Sundays from 15.001 for 3 hours (and
0 minutes).
Of course, you can specify a set of several "time spec" strings in order to obtain several modes of operation from the same time queue.
Note: By means of EtherShare Admin you can only define one "time spec" string at a time.
Note: Entries in this preference specify when a print job
is forwarded to the hold queue. Therefore, setting printtimes is only meaningful if a hold queue is already set.Specifies a comma-separated list of printer queues to which print jobs are cloned (duplicated) from the original queue.
Specifies the Windows name (or the IP-address/host name) of the PC which the printer is connected to.
If a file is sent to a Windows printer queue, with this option set to FALSE, the print job remains "untouched" and is passed on without any changes.
Specifies the PCShare export name of the particular printer. The setting reflects that of the SMB Name: field in EtherShare Admin's Printers: configuration window.
Specifies if the particular printer is published for SMB clients, i.e for PC clients. The setting reflects that of the checkbox Windows - SMB in EtherShare Admin's Printers: configuration window.
| © 2002 HELIOS Software GmbH |
|
|
|
|
|
