|
|
|
|
|
HELIOS Base UB User manual |
||||
Note: The usage for many of the HELIOS utilities can be listed at the command line by following the command with -h, for "help".
The "srvmsg" program allows a UNIX user to send a message to connected HELIOS AFP, SMB, or Admin clients, to trigger the reconfiguration of a process, to set or change auditing options, or to start live auditing for a process.
Send a message to one or more users connected to the host. The users are selected with the -n, -p or -u option. The number of characters in a message is limited to 255.
Send a "reconfigure" message to one or more processes. The processes are selected with the -n, -p or -u option.
Set auditing output options for the specified process. You must be "root" or owner of the process to use this option.
Start live auditing of the specified process. The auditing output is printed to standard output. The auditing is automatically turned off when you press Ctrl-C. You must be "root" or owner of the process to use this option.
Note: The following options are used with -m and -r to specify the users/processes where to send a message. If no process is specified, the message is send to all users/processes. This can be done only by the user "root".
Send message to a particular user. If the user is logged-on more than once, the message is sent to all processes of that user.
Note: The following option is used with -d.
Induce process to send auditing output to the specified file. If the file already exists, the auditing output is appended to the file. Auditing is turned off with -f "". We recommend to use the -D option which automatically turns auditing off when Ctrl-C is pressed.
Note: The following options are used with -d and -D.
Specify the output options for auditing. Options can be "all" or a comma-separated list of the following options:
This command sends a flush/reconfigure to all "pcshare" processes. It forces "pcshare" to flush all files and to release unused resources.
Log files, such as printer or server log files, are modified with each new login on the respective server. To maintain a certain order, they can be allocated a particular file name extension, e.g. by an ascending numbering. E.g. the printer log file which records the entries of today may be named "printer.acct", the one with yesterday's entries "printer.acct.0", and so on (see A 3.1 "Printer log file structure").
It may be reasonable to determine a cycle after which the oldest log file is discarded, e.g. after one week. "logrotate" coordinates the "rotation" of the log files with the following parameters.
Octal expression for the file access rights. For example, 664 means that "owner" and "group" have the right to read and write, whereas "others" are just allowed to read the file.
The "locktable" utility shows which files are locked by the HELIOS processes. Note that you must be "root" to call the "locktable" command.
(clean-up mode): Delete all locks in the locktable which are held by processes that do not run anymore.
An important HELIOS feature related to the protection of your files is cross-platform file and record locking. HELIOS EtherShare and PCShare coordinate together to enable this feature. Without it, Windows applications are unaware when a Mac user has a file open, and vice versa. This means that they would be able to open and modify the same file at the same time, which could result in data loss. EtherShare and PCShare prevent this by accessing the same "locktable" file which allows cross-platform file and record locking even between Macintosh and Windows workstations.
Note: Some applications do not support file locking, so it is prudent to verify this capability.
The "migrate" utility allows you to convert EtherShare and PCShare configuration files into preferences (though it is recommended that the 4.3.1 "Migrate Settings" feature of the HELIOS Installer be used instead). Beginning with EtherShare 3.1 and PCShare 3.1, all configuration settings are stored in one single file ("Preferences"). It is necessary to state the path which leads to the "old" EtherShare/PCShare (-e, -p) location in order to enable "migrate" to find the old configuration file. Additionally, the volume's character set encoding must be stated (-E MacRoman,
-P PC850, or -E SJIS). The following options specify what is to be migrated:
EtherShare and PCShare volumes will be migrated. If you do not want to migrate the PCShare volumes, the -p option can be omitted (-e for EtherShare).
The "afpvolumes" file is evaluated for HELIOS volumes. Here is an example for an entry in this file:
For PCShare volumes the "exports.pcs" file is evaluated. Here is an example for an entry in this file:
The following files are evaluated for EtherShare printers ("atalk.conf", "Preferences", "/etc/printcap"). Only those printers which have an entry in "atalk.conf" and in
"/etc/printcap" are migrated. The "printcap" entry for a printer is taken on - except for the entries "lp", "if", "of", and "af". These receive HELIOS specific entries. The following spooler types are recognized in "atalk.conf":
The spooler type, which was implicitly provided in "atalk.conf" through specific flags is set explicitly now in the "Preferences" by IfType=<Type>. Other flags keep their names, but are stored in the "Preferences". For example, the parameter "jobholdtime" in the following excerpt from "atalk.conf" was taken on in the "Preferences" unchanged:
The file "/usr/local/es/conf/afppasswd" is copied to
"HELIOSDIR/var/conf/passwd". This file is indispensable if the Encrypted Password Transport feature (compare 4.6 "HELIOS TCP/IP security overview") is enabled.
Network interfaces entries and zones entries in "atalk.conf" are migrated. They start with the following key words:
Adapts the browsing and WINS settings from PCAdmin to the preference pattern, which was introduced with CD18.
The "uniconv" program, a new Unicode conversion utility, allows the conversion of text strings from one character set encoding to another, e.g.:
<InputScriptName> and <OutputScriptName> can be one of the available encodings or UCS16 for 16-bit MSB Unicode. The default is UCS16.
The "socket" command reads data from STDIN and sends it to a specified server. It also implements some functionality to measure throughput of data for message passing.
Using TCP based connections <server> and <port> can be used similar to telnet. If <server> is omitted, socket connects to "localhost".
Cause socket to print debugging messages about its progress - this is helpful in debugging connection
This call generates 10000 packages filled up with "A"s. Package length is set to 3072. "Socket" is using a TCP connection to server 172.16.7.155 on port 12345.
The "swho" command can be used to list all currently active HELIOS child server processes, together with the process ID (PID), the network address (EtherShare:
AppleTalk/IP address or name; PCShare: internet address or client name), user name and process starting time:
In this example you can see three logins via AppleTalk (one "afpsrv" and two "termsrv" connections) and two logins via "PCShare", one of them from a PC client as a guest user ("nobody"), and the other from another PC with the user name "anyuser". A separate PCShare process is started for each user login (including guest logins - user "nobody"), although a single process can support multiple drive and/or printer connections, even if they are all mounted at the same time.
The name of the PCs ("tecra" and "Office" in the above example) is only shown if the PC has been specified with name and IP address in "/etc/hosts" or in the equivalent host database, such as NIS. If the name is not specified, the internet address is shown instead of the computer name:
Include an optional comment field, which shows more information about the session. PCShare servers show the name of the corresponding mounted UNIX directory or print command, EtherShare file servers ("afpsrv") show the names of the currently mounted HELIOS volumes. In addition, sleeping clients are displayed in the Comment column:
"swho" gets its information from the file "stmp", which is updated by both PCShare and EtherShare servers. "stmp" is located in the "HELIOSDIR/var/run" directory.
Suppress DNS (Domain Name Service) lookup functionality. If this option is set, the network address appears as IP number instead of the name.
Note: If "swho" delivers quicker results with the -n switch set you probably have a DNS configuration problem.
Clear the "HELIOSDIR/var/run/stmp" file from entries which are orphans, i.e. cannot be allocated to current processes anymore.
Related information is available from the host's current services list. In the following example, we use the "srvutil status" command (see 13.1 "srvutil") to display the services:
HELIOS file and print server functionality is all implemented in a single "helios" master process, which spawns a child process each time a user mounts volumes or print queues.
"ifstat" is a handy utility to see the AppleTalk network settings for each of the server's network interface cards. Additionally, with the -l option specified, "ifstat -l" returns the IP number and subnet mask of the local subnet:
These values can then be added to the default "ipaccess" list, in order to limit access to HELIOS services to only those nodes on the local subnet. The default "ipaccess" list does not provide any access restrictions to the host. See also 4.6.2 "IP Access Control Lists", and ipaccess.local in 5.8 "HELIOSDIR/var/conf".
Note: Though "ifconfig" offers more extensive network interface information, "ifstat" includes AppleTalk settings.
This chapter describes the "dt tools", which mimic the functionality of some major UNIX commands for handling files, while maintaining the integrity of the desktop database. "dt tools" also provide access to Macintosh specific file information from a UNIX prompt.
Important: The "dt" program does not consider any file locking and can therefore also copy files in use. In order to avoid damage, consider this and make sure nobody is working concurrently on these particular files before manipulating them with "dt".
If you access all files from a Macintosh only, you do not need to read any further. But if you need to access files which are stored in a HELIOS volume from the UNIX prompt, there are a lot of reasons for using the "dt tools".
Note: "UNIX prompt" here means any access under UNIX, e.g. any script or program (like a backup program), which accesses files stored in a HELIOS volume.
Any manipulation to a file or folder inside a HELIOS volume using ordinary UNIX commands like "cp", "mv", "rm" or other programs, will cause an inconsistency between volume information and the related desktop database. Especially restoring files from a backup will trigger such an inconsistency.
In the following sections, you will find more information on this problem, and on how the "dt tools" help avoid it.
A file in the Windows/NTFS environment can have a certain number of file streams. File streams contain meta data such as document title, subject, author, etc., similar to the resource fork of a Macintosh file.
The "dt tools" can handle Windows NTFS file streams. On access to a file on the network that has been created in the Windows/NTFS environment, e.g. rename a file, move or remove a file on a HELIOS server, all pertinent file streams are considered as well.
Use the utilities whenever you would (usually) use any of the following UNIX commands (if either source and/or destination files/folders are located in a HELIOS volume):
You may use the "dt" utilities even if the source or destination is not located in a HELIOS volume, or if you are not sure about this. The "dt" utilities automatically select the proper mode of operation.
It is required to use the "dt" utilities together with EtherShare, PCShare and/or ImageServer. These HELIOS products have improved verification mechanisms to recognize potentially harmful configurations, and will disable access to volumes for which consistency between volume and desktop information cannot be assured. In addition, warning or error messages are logged to the system error log file, which may help you locate the cause of the problem.
Just to help you understand the possible error messages and the specific behavior of the "dt" utilities, here are the main differences to standard UNIX commands:
- Each Macintosh file consists of two parts, the so-called "data fork" which is stored as a standard UNIX file, and a corresponding "resource fork" which is stored by Base in an ".rsrc" subdirectory. Additional information for each file is stored in a corresponding entry in a volume based "desktop" database. Therefore, when using UNIX commands, each operation like move, copy, or delete, must consider both the "data fork" and "resource fork" as well as the database entry instead of just one single file.
- When looking into a volume as a UNIX directory you may not notice the differences, because the resource fork subdirectory and the database files are stored as hidden UNIX files.
- The "dt" utilities simulate the behavior of standard UNIX commands as close as possible, but there are slight differences in the number and functionality of the available options, and due to the extended functionality you may notice a different behavior and different error messages. For example, you may see error messages about the resource fork of a file, which you would not see when using standard UNIX commands (the UNIX commands - in fact - ignore this part of the file).
- For all of the "dt" utilities commands, a behavior that differs from that of their UNIX counterparts may be visible. This is due to the fact that different semantics are used by Macintosh Finder operations on the one side and UNIX file system operations on the other. The "dt" utilities will behave like an "afpsrv" on recognized HELIOS volumes, and will behave like ordinary UNIX commands like "cp", "mv", "rm", in areas where no HELIOS volume is defined. The "dt" utilities will process data and resource part of files and will also assure that ownership and permissions are compatible to the Macintosh Finder operations. See also "Directory and file formats", and "Users and groups" to "Access privileges".
Before you try and use any of the "dt" commands, you should be well familiar with the corresponding UNIX commands. If you need more information about how the "dt" utilities work and how problems arise without the utilities, please read the "Technical notes" following each command description, and 7.9.3 "Additional information".
We do not recommend to sym-link regular "cp", "mv", "rm" commands to the "dt" utilities. Although this is possible, you should verify your current and future system environment very carefully, to assure proper operation of your programs, scripts and established workflow.
Especially, you should check whether your site uses special HSM (Hierarchical Storage Management), tape robot, or RAID (Redundant Array of Independent Disks) software which may also use their own versions of these UNIX commands. Take into account that different users and script based programs may make use of different shells and environment settings.
We suggest to check for each HELIOS volume the consistency between the volume information and the volume's desktop database. HELIOS Base offers a rebuild option, namely -s (scan only), which can be used for this purpose (see 7.10 "rebuild").
Simply issue rebuild -s <volume mount point> for every defined public or private HELIOS volume. Any output of this "scan" indicates a potentially harmful inconsistency between volume and desktop information. You should only continue after having re-synchronized the desktop database by means of an ordinary rebuild.
Take some time to make yourself familiar with the utilities and the way they behave inside a HELIOS volume, between different HELIOS volumes, and between non-HELIOS and HELIOS volumes.
The "dt" utilities use standard error messages starting with the program name (including the command argument), followed by the file or directory currently processed, and the error message, e.g.:
The error messages used are similar to the errors issued by the standard UNIX commands. Please note that you may encounter additional error messages regarding the resource fork or the desktop database.
In some cases the "dt" utilities may issue error messages displaying the full path of a file name instead of the passed relative one. This is due to the fact that the desktop database always needs absolute file names instead of relative ones. In this case, you may see the completely resolved (including symbolic links) absolute path name in the error message.
For the following command descriptions the knowledge of the functionality of the corresponding UNIX commands is assumed. Please refer to your UNIX manual if you are not familiar with the commands.
If you do not need or want to know, how the "dt" utilities operate, you only need to read the main command description for each UNIX command which is emulated by the "dt" utilities. The technical description following each command is meant for advanced users or system administrators, and explains some details or the special behavior of the respective command.
With very few exceptions, "dt" behaves identically on all HELIOS-supported platforms. Please note that, for this reason, some platform-specific options could not be implemented.
For all commands, the standard UNIX permissions apply when accessing, removing, or overwriting a file.
These files are handled implicitly by "dt" and there is no need to specify them directly. You should never move, copy, or remove these files with other commands, as e.g. the standard UNIX tools. Do not manipulate them at all.
Note: In the following, the term "volume" is used for a directory that is defined as a HELIOS volume which contains a desktop database (in contrast to a simple UNIX "directory").
Note: In the following, the term "volume root" means the top level folder of a HELIOS volume. The "HELIOS Applications" volume, for example, is by default defined to reside in "/usr/local/helios/public", which is its "volume root" directory under UNIX.
"dt" will recognize access to HELIOS volumes from another server only by means of available ".DeskServer" files.
"dt" may process files/folders differently, depending on whether the source/destination of the operation is inside/outside a HELIOS volume. The Macintosh Finder and the UNIX file system use different semantics, and "dt" assures that in HELIOS volumes the Macintosh semantics will be applied. The differences are mainly visible in permissions/ownership.
"dt" will process data and resource parts of files/folders in HELIOS volumes. If no resource information exists, "dt" will be able to create at least minimum information. Especially copy or move operations may require more free space on destination file systems.
Usage: dt { rm | rmdir | mv | cp | set | ls | mkdir | touch | upd | chmod | chown | chgrp | idinfo | iddump }
Calling "dt" with the command argument but no further arguments, prints the usage for the specific command, e.g. calling dt rm prints:
-i Prompt for confirmation for each file. If the
answer begins with y (yes), the file is deleted,
otherwise the file remains.
Note: Missing resource forks are not reported unless the -v verbose option is set.
The volume root directory is automatically touched to announce the changes to any Macintosh that has mounted the volume.
When removing a directory using the -r option, "dt" automatically tries to remove any orphan resource forks. The volume root directory may only be removed, if this volume is not in use by any other client, either EtherShare or the "dt" utilities, otherwise a "directory not empty" error is issued.The "dt rmdir" command will remove the directory entry specified by each dirname operand, provided that this operand refers to an empty directory.
-p Allow users to remove the directory dirname and
its parent directories which become empty. A
message is printed on the standard error about
whether the whole path is removed or part of the
path remains for some reason.
- Move a file "f1" to the destination file "f2"
- Move the passed files "f1- fn" into the destination directory "d1"
- Move the passed directory into the destination directory "d2", and create "d2" if it does not exist
-c Move a file from one HELIOS volume to another
HELIOS volume with a different character set
without converting to the target volume
character set or reporting error messages.
Important: If you do not use the -c option with the "dt mv" and "dt cp" commands, an error message only occurs if you copy/move files from a HELIOS volume to another. Copying/moving from a UNIX directory will not provoke any warning at all and might irritate the ".Desktop" file.
-f Move the file(s) without prompting even if it is
overwriting an existing target. Note that this is
the default if the standard input is not a terminal.
-i Prompt for confirmation for each file. If the
answer begins with y (yes), the file is moved,
otherwise it remains where it is.
-k Keep ID, try to allocate the source ID and use it
for the destination as well (see
7.9.4 "Using "dt" for backup/restore"). In case
this is impossible, you will only get a warning
if -v is set. You can use this parameter to
preserve proper working of Macintosh aliases.
-z Force zero ID for destination, please refer to
"Zero IDs" and
7.9.4 "Using "dt" for backup/restore".
The behavior of the different UNIX implementations differs if both, the -f option and the -i option, are set. "dt mv" uses the following rule: if both the -f option and the -i option are set, this is not considered an error; here, the -f option will override the -i option.
If you move a directory between two HELIOS volumes, "dt" cannot simply move just the directory entry. The Macintosh Finder would have to perform two steps for this operation, namely copying a folder from one volume to the other and then deleting the folder on the source volume. "dt" has a similar task to accomplish. For every file and folder within the directory to move, first the object must be moved to the destination volume and registered in the destination desktop. Then, the moved objects must be deleted from the source volume and unregistered from its desktop database.
Please note that any Macintosh files/folders to which aliases are pointing, will have lost their connection after successfully been moved between volumes. This would be the same if you used the Macintosh Finder for this operation.
If source and target directory are on different file systems, "dt mv" copies the file and deletes the original; any hard links to other files are lost.
Volume root for both source and destination, is automatically touched to announce the changes to any Macintosh that has mounted the volume.
Please note that whenever the destination is a volume, the volume specific permissions will apply, meaning that the file you have moved will automatically inherit the permissions of the directory it has been moved to.
Usually, if a file is copied to a directory without a desktop (pure UNIX directory), the file ID is set to zero. When using the -k option, the file ID is maintained (if possible).
Even though the execution bit of the data fork should be masked out (according to the permission handling implemented by "afpsrv"), this is often inconvenient to UNIX users. Therefore, any existing execution bit is preserved by default.
- Copy a file "f1" to the destination file "f2".
- Copy the passed files "f1- fn" into the destination directory "d1".
- Copy the passed directories into the destination directory "dn".
-c Copy a file from one HELIOS volume to another
HELIOS volume with a different character set
without converting to the target volume
character set or reporting error messages.
-f Copy the file(s) without prompting even if it is
overwriting an existing target. Note that this is
the default if the standard input is not a terminal.
-i Prompt for confirmation for each file. If the
answer begins with y (yes), the file is copied,
otherwise it is not.
-z Force zero ID for destination, please refer to
"Zero IDs" and
7.9.4 "Using "dt" for backup/restore".
The volume root directory for both, source and destination, is automatically touched to announce the changes to any Macintosh that has mounted the volume.
If your source does not have a resource fork, and your destination is a volume, a default resource fork is created. Please do also take into account that every default resource will require 64 bytes, thus using the minimum disk block size on the destination file system. If there is only little free disk space on the destination volume, first check whether the destination file system can store all of the files. You can roughly calculate 1K (fragment size) per file/folder. Consult your UNIX system administrator or the appropriate pages in your UNIX manual for information on how to retrieve more exact information about your file system settings.
Even though the data fork execution bit should be masked out (according to the permission handling implemented by "afpsrv"), this is often inconvenient to UNIX users. Therefore, any existing execution bit is preserved by default.
"dt set" modifies the additional file information stored in the file's resource fork. For more information about the flags and fields used here, please refer to your Macintosh documentation.
You can use HELIOS Admin to extract the creator/type information an application sets for certain icons. For a description see "Extension Mappings" in the EtherShare manual and the content of "HELIOSDIR/var/conf/suffixes".
-L int. Set the file to number of allowed concurrent
program launches, where "integer" is the
number of launches.
-C Clear the file ID numbers in the resource
fork (set to zero) and force the "afpsrv" to
allocate new ID numbers.
Please note that you may list these information using
"dt ls". If you need to set type or creator info with non-printable values, you may as well enter these values as octal values with a preceding backslash ("\"), and use the following escape sequences:
Please note that for both type and creator, all characters including 0 are valid. Each passed creator or type must be exactly 4 bytes long.
When you call "dt set" for a file without a resource fork, a default resource fork updated with the passed parameters is created, even if the destination file is not located in a HELIOS volume.
Please note that "dt set" does not create a missing ".rsrc" directory; use "dt touch" first on the file name in order to force creation of a related ".rsrc" subdirectory where the file's resource information can be stored.
Each Macintosh file on a HELIOS volume has an ID number that is stored in both its resource fork and the desktop database. The "dt iddump" command outputs all file IDs of the volume in question (specify volume path) from the desktop database to "stdout".
For each file that is a directory, the contents of the directory is listed; for each file that is an ordinary file, the name and resource related information are listed. When no argument is given, the current directory is listed.
-a List all entries, including those beginning with a
dot character ("."), which are normally not listed.
-x Force printing of non-printable characters for
type and creator, which are normally shown as
underscores ("_"), in the hexadecimal "\xdd"
notation.
-o Force printing of non-printable characters for
type and creator, which are normally shown as
underscores ("_"), in the octal "\ddd" notation.
-m Print file name stored in the desktop database
instead of UNIX name. If any difference
between these names is detected, both names are
shown. If the target directory does not have a
corresponding desktop, this option is ignored.
-i For each file, print the file or directory (as stored
in the resource fork) and the parent id (as stored
in the desktop database).
This information may not be correct in case
files/folders were manipulated with UNIX
programs other than the "dt" utilities.
Use rebuild -s to verify consistency between
volume and desktop information.
Please note that Macintosh aliases cannot be created with the "dt" utilities. The internal structure of aliases is not documented by Apple.
This command prints the names of all files in the passed directory "/support/temp", showing the file attributes, the type and creator for that file and its name. Please note that directories do not have any type or creator and therefore the fields are empty for directories.
Often you may wish to include more Macintosh specific information in the output. You can use the -l option for that:
Here you see the attributes, the ID, parent ID, type, creator, Macintosh date, size of the data, size of the resource fork, and the file name.
Please note that the output format (e.g. time format) depends on the current settings for the local environment.
The "dt mkdir" command creates the passed directories including the corresponding resource fork and the desktop database entry.
-p With this option, mkdir creates "dir" by creating
all the non-existing parent directories first. The
mode given to intermediate directories will be
the difference between 777 and the bits set in
"umask".
Note: If no mode parameter is set, the final directory is created in mode 777 considering the file mode creation mask "umask".
The command "touch" sets the access and modification times for the passed files. A file is created if it does not already exist.
The "upd" command touches the volume directory for the passed file or directory, so that all Macintosh computers that have mounted this volume can display the changes. This may be necessary e.g. if a file is created under UNIX and the Macintosh would display the new icon only after closing and re-opening the corresponding window.
Please note that all "dt" commands automatically update any needed volumes; so this command is only required, if files are created or changed by other, non-"dt" commands. Check whether you can adjust your workflow to "dt" commands and thus avoid potentially harmful non-"dt" commands.
Note: Macintosh clients only scan for changes every 10 seconds. Usually, folder information are updated within this 10 seconds period. However, depending on folder sizes, number of folders open, foreground applications, etc., this may take longer. Thus, it may take some time after issuing an "upd" command, before the changes become visible on the client. You can either click into the folder window, or close and re-open it in case the displayed information do not seem to be up-to-date. In rare situations, it may be necessary to unmount and remount the volume in question in order to let the Macintosh flush its cache entries. Make sure that you are using the latest Macintosh OS and up-to-date AppleTalk/Network drivers.
-n Change directory only - not the files within the
directory. The default behavior of the "dt chmod"
command is as follows:
If a pure UNIX directory is changed, the changes
are applied to the directory only. Else, if a
directory in a volume is changed, the changes are
applied to the files within this directory as well
(they are not applied to subdirectories). The -n
option makes sure that the command is always
applied to the directory only.
An absolute mode is specified using octal numbers (0-7), please see the UNIX documentation for a full description.
A symbolic mode specification is a comma-separated list (without any intervening spaces) of symbolic mode expressions of the form:
In order to adjust permissions to files/directories and their related resource parts, you must own the directory in question. In case the resource directory does not match the enclosing directory's permissions, "dt chmod" cannot adjust the ".rsrc" directory's permissions. You have to log in as "root" in order to synchronize permissions of the two directories. Please refer to the UNIX documentation for a full description.
dt chmod a=rwx,g+s file
sets read ("r"), write ("w"), and execution ("x") permission for all ("a") users, and adds group set-ID mode ("s") for groups' permissions.
The "chown" command sets the user ID of the passed file to the new user ID specified by owner, and, optionally, the group ID to the new group.
-h If the file is a symbolic link, change the owner of
the symbolic link (not the owner of the file that is
referenced by the symbolic link). This option is
not supported on all platforms.
-n Change directory only - not the files within the
directory. The default behavior of the "dt chown"
command is as follows:
If a pure UNIX directory is changed, the changes are applied to the directory only. Else, if a directory in a volume is changed, the changes are applied to the files within this directory as well (they are not applied to subdirectories).
owner[:group] (use "." or ":")
A user ID and an optional group ID to be assigned. Both IDs may either be specified by the numeric ID or by the corresponding user or group name.
Please note that you need the necessary access rights to change the user or group ID of a file - according to UNIX semantics, only the user id "root" is allowed to change ownership settings.
-h If the file is a symbolic link, change the group of
the symbolic link (not the group of the file that is
referenced by the symbolic link). This option is
not supported on all platforms.
-n Change directory only - not the files within the
directory. The default behavior of the "dt chgrp"
command is as follows:
If a pure UNIX directory is changed, the changes
are applied to the directory only. Else, if a
directory in a volume is changed, the changes are
applied to the files within this directory as well
(they are not applied to subdirectories). The -n
option makes sure that the command is always
applied to the directory only.
Please note that you need the necessary access rights to change the group ID of a file - according to UNIX semantics, only the user id "root" is allowed to change ownership settings.
The main purpose of this command is problem detecting. The Macintosh file, or respectively directory ID, is stored in both the file's resource fork and the desktop database. The ID stored in the resource fork may be listed by using the "dt ls" command.
The "idinfo" command may be used to display database information for the passed ID. If there is no difference between the resource data and the corresponding database entry, you should get the same information, otherwise the system administrator should issue a "rebuild" for the specific volume. You can use rebuild -s <volume root> to verify that the volume information is properly reflected in the related desktop database.
Please note that each volume has its own ID scope. Therefore, you must specify the correct volume for each ID you request. If you do not specify a volume with the -v option, the current working directory is assumed:
volume: '/support' id=3159 pid=2 name: 'temp'
specifying the volume detected, the ID, the parent ID for this file, and the corresponding name stored in the database.
Note: Please note that an ID detected in the database that does not have any corresponding file in that volume does not cause any problems or data loss.
For almost all of the described "dt" commands (except for "upd", "idinfo", "iddump") the -X option can be applied:
Usually, the desktop of a volume is kept open for about 30 sec. when being used by "dt" in order to avoid overhead (desktop database completely open/closed). This is because further access is to be expected. However, for certain applications it is not advisable to block the desktop for a volume that long. Hence, with the -X option the desktop close delay can be suppressed.
This warning message appears if you intend to move a file from one HELIOS volume to another, and the volumes' character sets do not match.
This warning message appears if you intend to copy a file from one HELIOS volume to another, and the volumes' character sets do not match.
The information in this section are mainly meant for system administrators who want to integrate the "dt" utilities into custom solutions, e.g. backup scripts. You do not need these information for the simple use of the "dt" utilities
(it does not hurt, however, to read on).
Each HELIOS volume is accompanied by a corresponding desktop database, which holds additional information about each file or directory stored on this volume.
Each file or directory in a HELIOS volume consists of two parts: the "data fork" and the "resource fork".
Though invisible to the Macintosh user, both parts of a file and the corresponding information in the desktop database are handled transparently and automatically by EtherShare.
If you also use ImageServer and/or PCShare these HELIOS products will also coordinate access to shared files/folders with the HELIOS volume desktop databases.
Looking at a volume from the UNIX point of view, you will find two files: the data fork as the "normal" UNIX file, and the resource fork in a subdirectory ".rsrc" with the same name.
Since UNIX files consist of only one part, but Macintosh files of two (see "Macintosh files under UNIX"), each pure UNIX directory ("UNIX-dir") should only have entries without a corresponding resource fork, and in a HELIOS volume ("volume-dir") each entry should have a corresponding resource fork.
If you now copy or move an entry from a "UNIX-dir" into a "volume-dir", "dt" always creates a default resource for this file. This is also the default behavior, if you move or copy a file from one "volume-dir" to the other.
If you copy an entry from a "volume-dir" into a "UNIX-dir", "dt" copies or moves the resource fork as well, even if the resource fork is not needed here. This is done in order to avoid any unintentional data loss. If you do not want to consider the resource forks here, you may use the -n option for the "mv" or "cp" command.
The "dt" utilities do not require the desktop server to run on the UNIX server where you issue the commands, but by default the "dt" utilities try to connect to the local desktop server on the server where you issue the commands first.
If this volume is already in use (e.g. mounted as a volume on a Macintosh) the "dt" utilities try to connect to the current server which serves this volume. This could be a different server, e.g. if this volume is mounted via NFS. Source and destination are handled completely independently, e.g. a source file for a copy command may be served by a local desktop server, while the destination directory which is located in a NFS-mounted directory is served by another HELIOS desktop server.
The "dt" utilities are unable to connect to a desktop server, when the target directory is not mounted by any Macintosh and no local desktop server is running. In this case start a local desktop server or mount this volume on a Macintosh.
The "dt" utilities will do an extensive verification in order to connect to the proper desktop server. Nevertheless, please verify your environment so that no single HELIOS volume can be accessed at the same time from different HELIOS servers.
Note: In case of different desktop servers being involved in a "move directory" operation, it may be necessary to traverse through directories instead of just moving the directory entry - see "dt mv" for more details.
Please note that you may unintentionally cause this problem by accessing an already mounted volume via auto-mounter:
On any mounted volume, the HELIOS file servers automatically detect any file which has an accompanying resource fork with a zero ID (the ID set to numerical zero) when the parent directory is opened from a Macintosh.
A file without a valid ID does not have any database entry, and therefore, a new desktop database entry is created, and the resource fork is updated using the new ID.
The "dt" utilities never create zero ID resource forks in volumes unless you force this behavior using the -z flag for the "cp" and "mv" commands.
Important: This option should only be used by system administrators - it is not intended for normal use.
One main purpose of the "dt" utilities is to avoid problems when restoring data from a backup device. Here we describe how you should use the "dt" utilities for backup/restore purposes:
You may backup your data as usual directly from your volume. Please make sure that the hidden ".rsrc" directories are included. To prevent backup of incomplete data in files, make sure that the files/folders to be backed up will not be manipulated from other Macintosh or UNIX applications. Only if you intend to do a complete backup and restore of a HELIOS volume you might include the ".Desktop" file. For the period of time you need to backup and restore this volume, HELIOS must be stopped with "stop-helios".
Important: Do never restore your data directly into the destination volume!
Please create a restore directory on the same device (partition) where the destination volume resides, e.g. if you intend to restore files into e.g "/data/mypics", create a directory "/data/restore". This "restore" directory must not be defined as a volume, or even being mounted. Now restore your data using your usual restore procedure into this newly created directory "restore". Make sure that you do not restore the ".Desktop" and ".DeskServer" files.
Important: Do never remove these files (".Desktop" and ".DeskServer") from a mounted volume or manipulate them directly. This may cause not only data loss for this volume, but may cause problems for all defined volumes on the server. In case you want to backup/restore these files, make sure that EtherShare and PCShare (if you are sharing volumes) are stopped completely prior to your backup/restore operation. Only if you stop HELIOS by means of "stop-helios" and stop access from other HELIOS servers, intermediate access to these files from HELIOS processes can be prevented.
Finally move the restored files into their final destination. This procedure avoids any data loss and may be used in a mounted destination volume.
Usually, new (unused) file IDs are assigned when you copy files to a backup destination. It may, however, be sensible to keep the file ID (using the -k option). Thus, the file can be re-used with its original ID. This is especially useful if you are using Macintosh aliases pointing to these files/folders. You should use this option sensibly. In case a complete desktop rebuild has been conducted after your backup operation, aliases may point to the wrong destination.
To avoid any problems, it may be a good idea to run an integrity check for the destination volume by entering rebuild -s on the command line, before restoring any files.
Note: If you are not familiar with desktop rebuilds, we strongly recommend to use the Rebuild Desktop- option in HELIOS Admin instead of the "rebuild" program. For volume conversions use the HELIOS utilities "convertvol" and "converthome", which are described in the EtherShare manual.
- If you want to rebuild the ".Desktop" database for your home volume or a private volume. The desktop server will create a ".Desktop" database and resource directories the first time you access your home volume from the client, and will rebuild it if it becomes corrupted, but you will not be able to rebuild it manually from HELIOS Admin because it does not appear in the volume list
The rebuild program offers an option to clean (delete) resource orphans. As discussed earlier, the File server creates resource files for files created by UNIX applications when the corresponding folder is opened. However, when you delete a file directly from the host, the matching resource remains untouched. (But when you delete a file from a Macintosh, the resource file is deleted, too.)
So particularly if your HELIOS volume contains a mixture of Macintosh files and UNIX-only files, after a period of time the volume will tend to collect a number of unused resource "orphans", wasting space. Calling the "rebuild" program will automatically delete the resource orphans. You would have to set the cleanorphans preference of the "rebuild" program to FALSE to prevent the program from automatic deletion. (see 16.7 "Rebuild preference keys").
In the case of CD-ROM volumes, or volumes such as magneto-optic (MO) cartridges which have been mounted with HELIOS Admin as "read-only", the desktop server first checks to see if a valid ".Desktop" file is available on the volume's root. This can be the case, for example, for MO cartridges which were previously mounted under EtherShare as "read-write", allowing a valid desktop to be created.
If a valid ".Desktop" file cannot be found (this will almost always be the case for CD-ROMs), the desktop server creates a temporary desktop file in the host's "/tmp" directory using a unique file name starting with "desksrv-". Since the files on the CD-ROM almost certainly have no resource forks in this case, the Finder will use the information that are available in the extension mapping table or show one of the about 20 generic EtherShare icons.
When it starts, the "rebuild" program first accesses the main configuration file "Preferences" to determine its configuration. 16.7 "Rebuild preference keys" lists the preferences, which can be changed if necessary by using the "prefvalue" command. See also 7.11 "prefvalue".
Setting and retrieving single entries in the preference database (see 16 "Preferences") can be done using the program "prefvalue" in "HELIOSDIR/bin".
The preference key is the whole string containing the preference key strings which are delimited by "/" characters.
Note: Please note that key names are case-sensitive!
Important: If the key comprises a path, the "/" characters within the path must be "marked" by preceding each with a
"\" character.value is the value the preference will be set to.
type is one of the following and may only be used when setting a preference:
"prefvalue" is the command, -k the preference key (here
Programs/pcshare/hostname), -t the value type (here str for string), and the last argument is the value to set (ankh).
"prefvalue" is the command, -k the preference key (here
Programs/pcshare/hostname), and -d the option to delete the preference.
Important: Use this command with caution! Make a backup copy of "HELIOSDIR/var/conf/Preferences" first.
Dumping preferences into a readable form can be done using the "prefdump" command in "HELIOSDIR/bin/".
"PreferencesFile" is the binary preference database file which exports the preferences. If omitted, the default file "HELIOSDIR/var/conf/Preferences" will be taken.
If "DumpFile" 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 the command "HELIOSDIR/bin/prefrestore".
"PreferencesFile" is the binary preference database file which imports the preferences from the file "DumpFile". If omitted, "HELIOSDIR/var/conf/Preferences" will be taken.
With the -c option set, all old preferences are deleted and then the new preferences are loaded. Without -c option, new preferences are loaded additionally to the already existing preferences. In doing so, those with the same key are overwritten.
Not all available preferences are set by default, which means that they are not listed in the "prefdump" output, and the HELIOS products 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 HELIOS default value, use prefvalue -k <key> -d to delete the preference entry.
"mail" is a cross-platform mail client. It is based upon the HELIOS libraries, which is the reason why it works independently from the used architecture, and why it can be used very well in a scripting environment.
The program delivers the e-mail to a SMTP server. The SMTP server can be specified via options or via preferences (see -m option below).
mail [-f sender] -t to-address [-c cc-address]
[-B bcc-address] [-s subject] [-e encoding] [-r replyto] [-m SMTPServer] [-b msgtext]
mail -h (for help info)
Comma-separated list of additional recipients whose addresses are not included in copies of the message ("Bcc:").
The mail message (text). If this parameter is missing the input is read from standard input, until the input is terminated or a line with only a dot "." is read.
SMTP server which is used for delivering the mail. If this option is not given, the value of the preference
"Global/Programs/SMTPHost" is used. If the preference is not defined, "mailhost" is used.
In addition, SMTPHost may also contain - apart from the actual address of the SMTP server - name and password for authentication:
For longer mail messages it is easier to put the message text into a temporary file and send the message with
The "hupd" command starts the HELIOS Update Installer, a tool which lets you conveniently install HELIOS updates. For a detailed description on updating the HELIOS software see 17 "The HELIOS Update Installer".
The "license" command starts a program which lets you conveniently enter software licenses in order to activate already installed HELIOS products. For a detailed description and for operation instructions of the license program see 4.4.1 "Entering a new license".
The "oiinfo" program allows you to view a list of all "OpenImage" plug-ins that are installed and available.
The program, by default, searches the directory "HELIOSDIR/lib/OpenImage/Plug-ins". Every file in this directory will be checked to find out whether it is a correct plug-in and - if so - what type of plug-in it is.
Found Plugin at /usr/local/helios/lib/OpenImage/
Plug-ins/opibase.so:
Magic is HeliosOpenImage.
Version is 1.0.
Module is HeliosBase
Module description is
"HELIOS ImageServer base functionality".
Module version is 2.8.
Furthermore, for every correct plug-in, the "oiinfo" program lists all included "OpenImage" managers.
Modtoc:
Sectiontype 1:HeliosUnixFs (Helios Unix Fs mgrs)
Sectiontype 1:HeliosNativeFspec (Helios Native Fspec mgrs)
Sectiontype 1:HeliosESFspec (Helios EtherShare Fspec mgrs)
Sectiontype 1:HeliosPCSFspec (Helios PCShare Fspec mgrs)
Sectiontype 1:HeliosAdjust (Helios Adjust mgrs)
Sectiontype 1:HeliosTiff (Helios TIFF mgrs)
Sectiontype 1:HeliosJPEG (Helios JPEG mgrs)
Sectiontype 1:HeliosEPSF (Helios EPSF mgrs)
Sectiontype 1:HeliosScitexCT (Helios Scitex CT mgrs)
Sectiontype 1:HeliosAdobePhotoShop (Helios Adobe
PhotoShop mgrs)
Sectiontype 1:HeliosPICT (Helios PICT mgrs)
Sectiontype 1:HeliosMacintoshIcons (Helios
Macintosh Icon mgrs)
Sectiontype 1:HeliosAdobePath (Helios Adobe Path mgrs)
Sectiontype 1:HeliosColor (Helios simple Color mgrs)
After that, you will get a list of "OpenImage"-registered managers. This specific list provides information about which managers are available for use.
Manager type : Color
Predicate : 17530
Version : 1
Quality : 127
Registered key is
Scope : (00269) HeliosColorAll
Filesystem : (00000) *
Filespec : (00000) *
Filecreator : (00000) *
Filetype : (00000) *
Filetype Extension : (00271) RGB
Manager supports raster images.
Manager supports the following capabilities:
Capability 1:
Supports colorspace mapping:
Maps colorspace from RGB to Bilevel.
Supports image valuating.
Supports inkset change:
Accepts imagedata with any inkset.
Produces imagedata with any inkset.
Supports bpc change:
Accepts imagedata with 8 bpc.
Produces imagedata with 1 bpc.
...
Capability 4:
Supports colorspace mapping:
Maps colorspace from RGB to CMYK.
Supports image valuating.
Supports inkset change:
Accepts imagedata with any inkset.
Produces imagedata with any inkset.
Supports bpc change:
Accepts imagedata with 8 bpc.
Produces imagedata with 8 bpc.
The "pstext" program in the "HELIOSDIR/bin" directory allows simple ASCII files and files in "nroff" format to be printed on PostScript printers. Since PostScript printers usually cannot accept print jobs consisting of "flat" ASCII data, it is normally not possible to print UNIX program listings or to print from UNIX programs that only support a simple matrix printer. The necessary conversion can be made with this program. "pstext" can also check the print job for special sequences starting with the "Esc" character, which can be used to control simple highlighting features such as bold printing, underscoring, and different fonts.
The HELIOS print server is able to differentiate "flat" ASCII data from PostScript data automatically, and calls "pstext" to convert the job accordingly. Thus, it is usually not necessary to call "pstext" manually. See also magic in 16.3 "Printer preference keys" for related information.
"pstext" is started from the command line in order to convert an existing file for printing, or from inside a host pipe in order to be able to directly print from an application without having to spool the ASCII print output to disk. "pstext" can be controlled with additional parameters in typical host style.
This command converts the file ".profile" to PostScript and sends it to the printer "lw". To do this, "pstext" calls "lpr" with the specified printer name. "pstext" first looks for "lpr" in the "HELIOSDIR/bin" directory and then in the directories specified in the hosts's path. If the option -P printername is omitted, the generated PostScript code is output to the terminal for test purposes, rather than to the printer.
The following is an example of the use of "pstext" in a host pipe. It outputs the current directory to the printer "lw":
Font with which the document should be printed. The default here is "Courier", because this is one of the few commonly available non-proportional fonts, which makes it particularly suitable for listings and tables.
Name of a PostScript language "prep" file which should be added to the start of each print job. If you do not specify the -e option, "pstext" automatically uses the internal "prep" file. This file contains definitions which are needed by "pstext". Instead of specifying an alternative "prep" file name in the command line with the -e option as above, you can set the name with the UNIX environment variable "$PSTEXT_PREP". This avoids having to specify the -e option. See the -d option below for more information about using and editing the "prep" file.
Title is automatically printed on the top line of each page. If this option is omitted, "pstext" automatically prints the file name and the date on the top line.
Specifies the space to the left paper edge in points. The default varies slightly from printer to printer, and is approximately 20 points.
Specifies the space from the top paper edge in points. The default varies slightly from printer to printer and is approximately 14 points.
Suppresses the title line. You normally want to suppress the title line if you are using the "pstext" escape interpreter, because you are probably printing with a more "intelligent" program which generates its own header in this case.
Print the date of the last modification to the file on the top line of each page, instead of the current date.
Specifies the distance of each tabulator stop in units of the width of the character "M". The default is eight, i.e. the width of eight "M"s ("MMMMMMMM") for each tab stop.
Name of the printer to which the file should be output. If this option is omitted, the generated PostScript code is output to the terminal ("stdout").
Can be set to dump the internal "prep" file "pstext.ps" to a file for further editing and use it with the -e option.
"pstext" can check the print job for special sequences starting with the "Esc" character, which can be used to control simple highlighting features such as bold printing, underscoring and different fonts. This is particularly useful for programs that normally work with a matrix printer. With such programs, it is often possible to enter the control codes to specify particular print attributes into a configuration table.
An escape sequence for "pstext" has three parts: The first is the "Esc" character (Hex 1B), which is then followed by a command (a digit between one and six), followed by the value of the parameter within square brackets, for example:
This escape sequence example shows how to include your own PostScript code (e.g. a trademark) during the printing procedure. It is important to store and restore the current position, which is why the program should always start with "gsave" and finish with "grestore".
"pstext" provides facilities to allow the PostScript coding (character set translation) of the printer font to be changed, for example to allow national accented characters such as Umlauts to be printed correctly. The default character set coding in PostScript only supports a few of the available accented characters. "pstext", however, re-codes the allocation of such characters by accessing the PostScript language "prep" file that is built into EtherShare. This file contains two different, modified versions of the so-called "Standard Encoding Vector", called "decEncoding" (for DEC Ultrix computers) and "ibmEncoding" (for IBM computers) respectively. Neither of these encoding tables are complete implementations of the corresponding character sets, they have only been set up to support the German Umlaut characters. However, they can easily be extended to add other special characters, or to specify completely new codings. Note that modification of the coding requires some knowledge of the PostScript language.
To edit the default "prep" file, you have to use the "pstext" program with the -d option. This dumps the "prep" contents into a file which can then be revised. We assume that the file name of the editable "prep" file is "pstext.ps".
The two alternative encoding tables can be found at the beginning of the "pstext.ps" file. They both function by copying the standard coding and changing it to add the required special characters. The following is the code table provided for the DEC VT200 character set:
dup 196 /Adieresis put
dup 228 /adieresis put
dup 220 /Udieresis put
dup 252 /udieresis put
dup 214 /Odieresis put
dup 246 /odieresis put
dup 223 /germandbls put
def
Each line of this table re-defines a single character. The decimal number (e.g. 196) is the decimal value of the character ("ASCII" value) in the input file's character set. This is followed by the PostScript name of the character. In PostScript, characters have names and not numbers. For example, "/Adieresis" is the PostScript name for "Ä".
The encoding tables are followed by a line which determines which of the two tables are used when printing. The table "decEncoding" implements a character set according to ISO 8859-1 (DEC VT200) whereas "ibmEncoding" implements a character set that corresponds to the IBM PC extended ASCII code. The following line in "pstext.ps" selects DEC encoding:
You can as well make a local copy of "pstext.ps" with a new - more individual - name, then modify this file, and specify its name with the -e option when calling "pstext", e.g.:
This command prints the file "testfile" using a new PostScript definition contained in the "prep" file "myprep1.ps".
The "psresolve" program acts like a printer driver, e.g. "papif". Instead of sending the PostScript output to the network, "psresolve" passes all PostScript data to "stdout" which can be redirected into a file or piped to an application.
Usually, new output parameters must be set. The "psresolve" program lets you set printer interface OPI-options manually on the UNIX server for one single print job. Options specified for "psresolve" override the settings in the preference database for the specific spooler:
In the following, we list the parameters that may be set with "psresolve" and then - at the end of this chapter - give you an example that may be used for a specific workflow.
Note: Parameters that can also be set in the HELIOS Admin dialogs are marked by the phrase "Compare HELIOS Admin!".
Printer interface related parameters are entered as command line options using the -o Preference=Value syntax.
This option turns OPI functionality on or off. If it is set to TRUE, OPI image replacement is enabled.
Specifies a list of path names where to search high-resolution images during image replacement, in case they cannot be found in the standard locations.
This parameter - if it is set to TRUE - enables the use of the EtherShare desktop database to locate moved image files.
This parameter - if it is set to FALSE - ensures that layout images are replaced with the corresponding high-resolution images for output. Otherwise, the layouts will be printed.
If this parameter is set to TRUE all fonts used in the document will be checked before printing. Every missing font will be reported and this will stop the print job.
If this parameter is set to TRUE all images placed in the document will be checked before printing. Every missing image will be reported and this will stop the print job.
Specifies whether special PostScript setup has to be included to avoid application specific problems during printout. This is necessary for FreeHand 3.1, PageMaker 5 and QuarkXPress 3.0.
If this parameter is set to TRUE, all images will be replaced during printout. Otherwise only layout images are resolved.
Specifies whether in case of resolving an already resolved PostScript job, the use of fonts and other resources should still be accounted.
This parameter specifies the path name of the default ICC-profile describing the printing device. Can be overridden using the HELIOS ColorSync 2 XT.
This parameter specifies the path name of the default ICC-profile describing the proof device. The string will only be recognized if a default printer profile is set. Can be overridden using the HELIOS ColorSync 2 XT.
This option - if it is set to TRUE - allows downsampling of images to a given output resolution. The value that has to be used for printing is specified by the Resolution parameter below.
This option allows to fix the downsampling resolution (see Resolution parameter below) to the given value. Usually, if this parameter is set to FALSE, the output resolution is adjusted to the image resolution if the image resolution is smaller. When setting this parameter to TRUE the printer interfaces will use the given Resolution as is for downsampling. This may cause upsampling of images with resolutions smaller than the given one. This parameter is only meaningful when setting the DownSampling parameter to TRUE.
This option controls the downsampling algorithm. By default, a bilinear algorithm is used. If you set this option to TRUE you switch to a fast picking algorithm. This parameter is only meaningful when setting the DownSampling parameter to TRUE.
This option controls the resolution of downsampled images. Zero induces the software to use the default resolution of the printing device as specified in the queue's PPD file. This parameter is only meaningful when setting the
DownSampling parameter to TRUE.
This option sets the color space used while printing separations. The default is CMYK for a four color print process. Spot colors are not affected by this parameter. Valid color spaces are "CMYK" and "Multi". If you set the string to "Multi" you have to define the names and order of the color components. Furthermore, the usage of the "Multi" color space requires the use of ICC profiles. For (future) ICC profiles that include the names of the color components, this option will become obsolete. Please note that the value you choose for this option can be overridden by the printer profile you have selected using ColorSync 2 XT or using the
DefaultPrinterProfile option.
This option controls, together with the ProcessColorspace option, the names of the process inks used for separations. Spot colors are not affected by this parameter.
This option sets the color space used while printing composite. The default is CMYK. Setting this option to None causes all color images in a print job to be kept and printed in their original color space. This applies to CMYK,
CIE- Lab and RGB images only. Valid strings are "CMYK", "RGB", and "CIELab". Please note that the value you choose for this option can be overridden by the printer profile you have selected using ColorSync 2 XT or using the DefaultPrinterProfile option.
This option selects a compression mode for images while being printed. CCITT Group 4, JPEG (Low to Max.), ZIP, and Compress are currently supported.
When printing layout images, ImageServer is able to scale down a high-resolution image to layout quality on the fly if the layout image cannot be found. This parameter controls the maximum resolution used for printing these transformed images.
Use this parameter to specify whether non-existing layout images should be ignored when printing layout quality.
This parameter enables the use of the ICC info files while printing images. If it is set to TRUE, every non-tagged image will be temporarily tagged during printing provided that the ICC info file specifies tagging for that kind of image.
This parameter controls whether non-tagged images should be ignored when printing to an ICC color matched queue.
This parameter - if it is set to TRUE - tells ImageServer not to resolve OPI comments if printing a PSImage file to an APR-aware RIP.
Note: The parameters which are described in the following two paragraphs will usually be specified when setting up EtherShare. They may, however, be relevant to ImageServer as well and can therefore be set as preferences, too.
IgnoreResolveOpts, IgnoreProcsetResolveOpt, IgnoreFontResolveOpt,
IgnoreIncludeResolveOpt and IgnoreOpiResolveOpt <boolean:FALSE>
When printing from an EtherShare spooler to a second EtherShare spooler, print jobs will usually not be resolved a second time. Specifying one or more of these options for the second spooler re-enables resolving of fonts, procsets, included files or OPI comments (IgnoreOpiResolveOpt).
Enables explanatory accounting. The accounting file will e.g. include the OPI image replacement list.
Imagine you want to print a document using the
CompressPostScript option. For that purpose, you have to change the default setting for this particular print job using the "psresolve" program. The complete procedure is described below:
First of all, set up two different printer queues using HELIOS Admin. One queue (e.g. "real_printing") is to be used for printing to an output device and the other one (e.g. "print_to_disk") is to be used for printing to a PostScript file (spool only).
Make sure that Spool only has been activated for the "print_to_disk" queue (Printer menu) and then print to this queue from your layout application.
Then, on your UNIX server, change to the spool directory that now contains your print job
(e.g. "/usr2/spool/print_to_disk"):
Start the "psresolve" program, enter the parameters you want to use, and specify the queue name, the input file name (e.g. "your_print_job") and the output file name:
# /usr/local/helios/bin/psresolve -o
CompressPostScript=Compress print_to_disk
<your_print_job >your_print_job_output
Finally, you may send the file "your_print_job_output" to your Spool & Print printer queue for output:
Please note that the "real_printing" printer queue will not resolve your print job once again. The job will be printed according to the settings that had been specified for the "print_to_disk" queue using HELIOS Admin and/or according to the parameters set by the psresolve command line.
The "start-helios" command starts all available HELIOS services on the host (see 4.5 "Starting/Stopping HELIOS Services manually").
The "stop-helios" command stops all HELIOS services on the host 5 minutes after entering the command. "stop-helios now" stops the services immediately, the -g parameter lets you specify the time until shutdown in minutes, and -m allows to issue a shutdown message (see 4.5 "Starting/Stopping HELIOS Services manually").
This command lists all HELIOS COM (Common Object Model) plug-ins which have been loaded by the HELIOS server. It helps verify available COM plug-ins and to monitor their status.
This is a tool to browse syslog entries. Records will be read from syslog files which are defined in "/etc/syslog.conf". All records will be mixed to one list so that records appear in chronological order.
Note: You must have appropriate access rights to the syslog files specified in "/etc/syslog.conf". Otherwise "psyslog" will issue an error message on the command line.
psyslog [[-d <date>] [-f]] (print syslog)
psyslog -t <tag> [-p <pid>] message ... (post to syslog)
psyslog -h (for help info) (print help)
<date> specifies a date to start listing entries from. Using all prints all entries from the beginning.
Causes "psyslog" not to stop when end of syslog file is reached, but to wait for additional data to be appended instead.
Post a message to syslog and exit. <tag> is used as identifier prefixing the message. Normally the program name is used here.
Continuously read syslog entries until "Ctrl-C" is issued. Output contains entries since "0:00:00" of the current day.
"htar" is a HELIOS implementation of a tar file compatible archive program. It is designed to handle specific features like Unicode file names, Macintosh Resource and Finder information, creation dates, Windows file streams, and attributes. "htar" allows moving files between UNIX and Windows and overcomes UNIX tar limitations.
On Windows, file streams and "Services for Macintosh" (SfM) are used. "dir/file:stream:type" is stored in the archive as "dir/file" and "dir/.rsrc/file:stream:type".
Use tar archive in <file>. If this option is omitted or given as "-", "htar" reads from from standard input (test/extract) or writes to standard output (create).
Be more verbose: print file names when creating or extracting an archive, print detailed information on files when testing an archive.
Keep Macintosh file IDs when extracting. Use this option with caution because the file IDs may conflict with file IDs of existing files on a HELIOS volume and "htar" does not add these IDs to the desktop database.
Note: Use HELIOS "xtar" to handle HFS Macintosh files. Details are given at:
http://www.helios.de/news/news03/N_06_03.phtml"printerlog" is a tool to list the "printer.acct" files in "HELIOSDIR/var/adm" in a human readable form.
| © 2005 HELIOS Software GmbH |
|
|
|
|
|