|
|
|
|
|
HELIOS Base UB+ User manual |
||||
8 HELIOS utility programs
Note: The usage for many of the HELIOS utilities can be listed at the command line by following the command with -h, for "help".8.1 srvmsg
The "srvmsg" program allows a 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.
srvmsg -m [-n server | -p pid | -u user] [-M file]srvmsg -r [-n server | -p pid | -u user]srvmsg -d pid [-f file] [-l level] [-o options]srvmsg -D pid [-l level] [-o options]srvmsg -hThe following options can be used with "srvmsg":
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.
Take the message from the specified file instead of the command line.
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 sent to all users/processes. This can be done only by the user "root".Send message to all processes of the specified server, e.g. "afpsrv" or "pcshare".
Send message to a particular process ID.
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 auditing level, e.g. "all". If -l is not given, a default level is used.
Specify the output options for auditing. Options can be "all" or a comma-separated list of the following options:
time short time stampfulltime long time stamppid process idname process namethread thread idflag flag namefile source file nameline source line numberfunc function nametabs tab-separated outputIf -o is not given, the following default options are used: time,pid,name,func,line,flag,func.
Example 1:
srvmsg -u neil 'Closing down all services!'A message with the content "Closing down all services!" is sent to user "neil".
Example 2:
srvmsg -r -n pcshareThis command sends a flush/reconfigure to all "pcshare" processes. It forces "pcshare" to flush all files and to release unused resources.
Example 3:
srvmsg -D 2990Start live auditing on process 2990. Live auditing is stopped with Ctrl-C.
8.2 logrotate
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").
logrotate [-n numlogs] [-m mode] [-o owner]
[-g group] logfileIt 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.
The following options can be used with "logrotate":
Number of accumulated log files before logrotate starts the "rotation".
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.
Group to which the file is allocated.
logrotate -n 6 -m 664 -o John -g helios printer.acct8.3 locktable
The "locktable" utility shows which files are locked by the HELIOS processes. Note that you must be "root" to call the "locktable" command.
Note: The "locktable" program is also referred to as the "Open files tool".locktable [-c]The following option can be used with "locktable":
(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. 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 Mac and Windows workstations.
Note: Some applications do not support file locking, so it is prudent to verify this capability.8.4 migrate
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 or 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:
/es/volumes/ethershare:EtherShare::fixed:readwrite:The fields are separated from each other by colons. All fields listed here are taken on:
Field Content1 UNIX path2 Chooser name3 password4 Flags1 (only fixed or changeable permitted)5 Flags2 (readonly, nopublish, noguest, charset=)6 Groups (separated by commas)For PCShare volumes the "exports.pcs" file is evaluated. Here is an example for an entry in this file:
disk "pcsvol" '/data/pcsvol' public,utf8,charset=PC850The following flags are accepted:
publichidedotfilesreadonlycloseclosefilesutf8charset=All EtherShare printers will be migrated.
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":
BalanceDiskHoldPAPTCPPreviewThe 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:
atalk.confhold: jobholdtime=21600Preferences[][Printers][hold][jobholdtime]flags=0type=Int32value=21600The 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:
zonezonesifinterfacenifninterfaceThe file "/usr/local/es/conf/afpipaccess" is copied to "HELIOSDIR/var/conf/ipaccess".
The file "/usr/local/es/conf/suffixes" is copied to "HELIOSDIR/var/conf/suffixes".
Spot colors which have been created by HELIOS Admin are saved to the new configuration.
Adapts the browsing and WINS settings from PCAdmin to the preference pattern, which was introduced with CD018.
8.5 uniconv
The "uniconv" program, a Unicode conversion utility, allows the conversion of text strings from one character set encoding to another, e.g.:
MacRoman to PC850
PC850 to UCS16 (16-bit MSB)
PC850 to UTF8
MacRoman to UTF8
SJIS to ISO8859-1uniconv [-v] <InputScriptName> [<OutputScriptName>]The following options can be used with "uniconv":
Convert Unicode to decomposite
<InputScriptName> and <OutputScriptName> can be one of the available encodings or UCS-16 for 16-bit MSB Unicode. The default is UCS16.
uniconv PC850 MacRoman <pcfile.txt >macfile.txt8.6 socket
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.
Connection can be done trough TCP or UNIX domain sockets (named pipes under Windows).
Using TCP based connections <server> and <port> can be used similar to telnet. If <server> is omitted, socket connects to "localhost".
socket [-v] [-k] [-r] [-b] [-m [-l <packlen>]
[-c <count>]] [<server>] <port>socket [-v] -u <path> [-e] [-b] [-m [-l <packlen>]
[-c <count>]]socket [-h]The following options can be used with "socket":
Size of receive- and sendbuffer
Tell the client how many loops to run the test
"Keepalive" sets parameter to keep socket connection alive
Size of a message packet the client should use for tests
Tell socket to do some message passing tests (see -b and -c)
Use a reserved port on client side (only "root" can do that)
Specify a path the UNIX domain socket should be bound to (on Windows, a named pipe is used)
Tell socket to discard received data
Cause socket to print debugging messages about its progress - this is helpful in debugging connection
Return the help info which also includes all service ports used by HELIOS software components.
Example 1:
socket -m -l 3072 -c 10000 172.16.7.155 12345This 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.
Example 2:
socket localhost 2002This call connects to the ImageServer service port 2002. Ctrl-C aborts the connection.
8.7 swho
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:# swhoServer PID Address User Whenpcshare 15984 tecra anyuser Thu 8:35afpsrv 56438 192.0.62.249 anyuser Thu 8:37termsrv 24730 192.0.62.158 anyuser Thu 12:56termsrv 23084 192.0.62.224 anyuser Thu 15:26pcshare 29610 Office nobody Thu 10:31#In this example you can see three logins via EtherShare (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:
# swhoServer PID Address User Whenpcshare 15984 192.9.200.85 anyuser Thu 8:35afpsrv 56438 192.0.62.249 anyuser Thu 8:37termsrv 24730 192.0.62.158 anyuser Thu 12:56termsrv 23084 192.0.62.224 anyuser Thu 15:26pcshare 29610 192.9.200.82 nobody Thu 10:31#swho [-f stmp_file] [-c] [-n] [-p]The following options can be used with "swho":
Specify file other than default "HELIOSDIR/var/run/stmp" file, from which "swho" information is generated.
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 -cAddress User When Comment192.0.62.249 applein Sat 14:32192.0.62.158 peter Wed 13:33 Apps,Helios,~peter192.0.62.224 peter Sat 15:35pc-max.dyn.h nobody Thu 8:42 /usr/local/helios/pub192.0.62.252 jum Thu 8:37 Programming,Helios,~jum192.0.62.144 anyuser Thu 12:56192.0.62.228 anyuser Thu 15:26 Public volume SLEEPING#"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 14.1 "srvutil") to display the services:
$ srvutil status
Service Status PID When Restarts srvsrv Running 287 Wed 10:08 notifysrv Running 289 Wed 10:08 authsrv Running 290 Wed 10:08 desksrv Running 291 Wed 10:08 heladmsrv Running 292 Wed 10:08 admsrv Running 294 Wed 10:08 afpsrv Running 295 Wed 10:08 mailsrv Running 296 Wed 10:08 papsrv Running 297 Wed 10:08 pcshare Running 298 Wed 10:08 lpd Running 299 Wed 10:08 termsrv Running 301 Wed 10:08 timesrv Running 302 Wed 10:08 websharesrv Running 303 Wed 10:08 opisrv Running 305 Wed 10:08 scriptsrv Running 306 Wed 10:08 createpdf Running 307 Wed 10:08 mdnsproxysrv Running 308 Wed 10:08 websharewoa Running 309 Wed 10:08 toolsrv Running 310 Wed 10:08 dhcpsrv Running 311 Wed 10:08 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.
8.8 ifstat
"ifstat" is a handy utility to see the TCP/IP and 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:
cd /usr/local/heliossbin/ifstat -lallow 192.168.123.0/255.255.255.0These 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 6.8 "HELIOSDIR/var/conf".
Note: Though "ifconfig" offers more extensive network interface information, "ifstat" includes AppleTalk settings.8.9 sqlite
This is a standalone public domain command line access program that can be used to administer an SQLite database and which serves as an example of how to use the SQLite library. The SQLite SQL documentation can be found here:
http://www.sqlite.org/docs.html
sqlite [OPTIONS] FILENAME [SQL]The following options can be used with "sqlite":
Print commands before execution
Set output field separator (|)
Set text string for NULL values
8.10 toolclient
The "toolclient" application is the front-end of the HELIOS Tool Server and is installed with the HELIOS Base installation. It is available on any HELIOS supported server platform. "toolclient" requires a valid ImageServer or PDF HandShake license. The tool client finds the tool server via mDNS ("Bonjour") or via a specified TCP/IP address. It can be integrated in any application by simply calling "toolclient" as an external application. HELIOS provides Script Server scripts for its included tools, this allows hot folder based job processing.
Find a description of the "toolclient" application in the Tool Server annual on the HELIOS website:
www.helios.de/support/manuals/manuals.phtml
8.11 "dt" tools
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 Mac 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 need to access files which are stored in a HELIOS volume from host scripts or commands, there are a lot of reasons for using the "dt" tools.
Note: Host commands 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 of a file or folder inside a HELIOS volume using ordinary UNIX commands like "cp", "mv", "rm" or other programs, will cause inconsistencies between volume information and the related desktop database, and you may lose additional data, e.g. file streams. Especially restoring files from a backup will cause such an inconsistency.
In the following sections, you will find more information on this problem, and on how the "dt" tools help avoid it.
Files and directories in the Windows/NTFS environment may 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 Mac file.
The "dt" tools can handle Windows NTFS file streams. While accessing a file on the network that has been created in the Windows/NTFS environment, e.g. renaming or moving it on a HELIOS server, all pertinent file streams are considered as well.
Also, file attributes such as Archive, Hidden, System, Creation date, label settings, etc. are also preserved when using the "dt" tools. In addition, a fast file search can be performed via the desktop database, with file ID support.
Use the "dt" tools 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" tools even if the source or destination is not located in a HELIOS volume, or if you are not sure about this. The "dt" tools automatically select the proper mode of operation, e.g. if source and destination are not volumes "dt" acts exactly like the corresponding UNIX program.
It is required to use the "dt" tools 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" tools, here are the main differences from standard UNIX commands:
- Each Mac 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 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.
- Windows files and directories may have additional streams as well.
- When looking at 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" tools 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).
- You may see different errors on "dt chmod", "dt chown", and "dt chgrp" because in volumes, you need permissions to change not only the specified file but also the associated resource directory, the resource file and all streams.
- For more information about resource and stream handling errors, you may use the -v (verbose) option.
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" tools work and how problems arise without the utilities, please read the "Technical notes" following each command description, and 8.11.2 "Additional information".
The "dt" tools do not require a special installation procedure.
We do not recommend to sym-link regular "cp", "mv", "rm" commands to the "dt" tools. 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 8.12 "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 tools and the way they behave inside a HELIOS volume, between different HELIOS volumes, and between non-HELIOS and HELIOS volumes.
The "dt" tools 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.:
dt rm notHere may result in the error message:
dt rm: notHere: no such file or directoryThe 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" tools 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.
8.11.1 Command descriptions
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 these commands.
If you do not need or want to know, how the "dt" tools operate, you only need to read the main command description for each UNIX command which is emulated by the "dt" tools. 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 platforms supported by HELIOS. 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.
"dt" checks each passed argument for the following names:
.Desktop
.DeskServer
.rsrcThese 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"). Likewise, the term "volume root" refers to the top level folder of a HELIOS volume. The "HELIOS Applications" volume, for example, resides by default in "/usr/local/helios/public", which is its "volume root" directory under UNIX."dt" will recognize a HELIOS volume by locating its desktop database ".Desktop" file.
"dt" will recognize access to HELIOS volumes from another server only by means of available ".DeskServer" files.
"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.
The following command modes are supported:
find Recursively descend the directory tree for each path name listed, evaluating an expression in terms of each file in the tree.
If called without any argument, "dt" prints the usage line:
Usage: dt { rm | rmdir | mv | cp | set | ls | mkdir | touch | upd | chmod | chown | chgrp | idinfo | iddump | find }Calling "dt" with the command argument but no further arguments, prints the usage for the specific command.
Many "dt" tools support the new options:
-X = Suppress desktop close delay
-y = Force scanning for streams
-E = Send events to notification server:
(-X option) 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 set, the desktop is closed immediately.
(-y option) Force scanning for streams that are not specified in the resource information of a file. If additional streams exist for a file but the file information is not marked for streams, this option checks the entire ".rsrc" directory if streams are detected for the current file. To avoid unnecessary search operations, the standard resource is marked if additional streams are available.
(-E option) If this option is specified, file events for all registered services are sent to the notification server.
The "dt rm" command removes the directory entry specified by each file argument.
dt rm [-firyXE] file-i Prompt for confirmation for each file. If the
answer begins with y (yes), the file is deleted,
otherwise the file remains.
In case of symbolic links, the link itself and not the file which the link refers to is removed.
If the standard input is not a terminal, the command will operate as if the -f option was set.
dt rm a.out core
removes the directory entries: "a.out" and "core".dt rm -rf junk
removes the directory junk and all its contents, without prompting.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 Mac that has mounted the volume.
When removing a directory using the -r option, "dt" automatically tries to remove any orphan resource forks or file streams. The volume root directory may only be removed if this volume is not in use by any other client, either EtherShare, PCShare, WebShare or the "dt" tools, 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.
dt rmdir [-psyXE] dirname-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.
"dt mv" moves the selected files or directories to a destination file or directory.
dt mv [-fiknvzcyXE] f1 f2dt mv [-fiknvzcyXE] f1 ... fn d1dt mv [-fiknvzcyXE] d1 d2The three different usages are provided for the following cases:
- 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". If "d2" does not exist, rename "d1" to "d2"
-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
8.11.3 "Using "dt" for backup/restore"). If this is impossible, you will only get a warning if -v is set. You can use this parameter to preserve proper working of Mac aliases.
-z Force zero ID for destination, please refer to Zero IDs and 8.11.3 "Using "dt" for backup/restore".
-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.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.
Important: If you move a directory between HELIOS volumes, "dt" cannot simply rename just the directory entry. Here, the Mac 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 copied 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.
This is similar to moving a UNIX directory to a different device, where also all affected files must be copied and then deleted, with the difference that here all resources and streams must be handled, too.Please note that any Mac file/folder to which aliases are pointing will have lost its connection after successfully been moved between volumes. This would be the same if you used the Mac 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 Mac that has mounted the volume.
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.
"dt cp" copies the passed files or directories to a destination file or directory.
dt cp [-fikpnvzcyXE] f1 f2
dt cp [-fikpnvzcyXE] f1 ... fn d1
dt cp -r[R] [-fikpnvzcyXE] d1 ... dn-1 dnThe three different usages are provided for the following cases:
- 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"
-f Copy the file 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 8.11.3 "Using "dt" for backup/restore".
-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.
The volume root directory for both source and destination, is automatically touched to announce the changes to any Mac 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.
"dt set" modifies the additional file information stored in the file's resource fork. For more information about the flags and fields used here refer to your Mac documentation.
You can use HELIOS Admin to extract the creator/type information an application sets for certain icons. For a description see 7.8.5 "Extension Mappings" and the content of "HELIOSDIR/var/conf/suffixes".
dt set [-t type | -c creator | -f file ] file ...dt set -l label color (0-7) file ...dt set -v [mini|symbol|name|date|size|type|label|button] dir ...dt set -a[-] [BisrlbpIPS] file ...
B:bundle i:Invisible s:system r:readonly l:lockedb:backup p:protected I:inited P:Package S:shareddt set -L launchcount file ...dt set -C file ...mini symbol name date size type label buttonMac WindowsB bundlei invisible Hiddens system Systemr readonly Read-Onlyl locked (norename, nodelete)b backupp protectedI initedP packageS shared[-] Preceding a flag clears that flag.-L 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 this information using "dt ls". If you need to set type or creator info with non-printable values, you may enter these values as octal values with a preceding backslash ("\"), and use the following escape sequences:
\b backspace
\n newline
\r carriage-return
\t tab
\f form-feed
\E escapePlease note that for both type and creator, all characters including 0 are valid. Each passed creator or type must be exactly 4 bytes long.
dt set -t "TEXT" -c "R*ch" file
sets type and creator for file using ASCII values.dt set -c "\001\002\003\004" file
sets creator for file using octal values.dt set -f mypic file
copies type and creator from "mypic" to file.dt set -ai file
sets the invisible flag for file.dt set -a-i file
clears the invisible flag for file.When you call "dt set" for a file without a resource fork, a default resource fork is created that is updated with the passed parameters, 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.
For each file that is a directory, the directory content 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.
dt ls [-1FSUacdiIlmnprstux] { -e [STBacdfiopstxy] } file ...-a List all entries, including those beginning with a dot character ("."), which are normally not listed
Extended flags (must be called with -e):
d:directoryA:aliasNote: Mac aliases cannot be created with the "dt" tools. The internal structure of aliases is not documented by Apple.B:bundleP:packagei:invisibles:systemr:readonlyl:lockedb:backupp:protectedI:initedS:shareddt ls /support/tempabc.movThis command prints the names of all files in the passed directory "/support/temp".
Sometimes you may wish to include more resource and stream specific information:
dt ls -l -ea /support/temp-rw-rw-rw- 1 -----r--p-- 5 'MooV' 'TVOD' jon admin 21988 Jan 5 2005 9:34 abc.movThis command prints the file mode (read-write access for owner, group, and others), the number of links (1), Finder attributes (read-only, protected), Desktop ID (5), type and creator (MooV, TVOD), user (Jon), group (admin), size (21988 bytes), date and file name (abc.mov).
Please note that the output format (e.g. the time format) depends on the current settings for the local environment.
"dt ls" uses user and group information from the authentication server (if running), otherwise only UNIX users/ groups are displayed.
The "dt mkdir" command creates the passed directories including the corresponding resource fork and the desktop database entry.
dt mkdir [-m mode] [-pyXE] dir ...-p This option 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".
dt mkdir -m0444 mydircreates the directory "mydir" with the passed modes.
Note: If no mode parameter is set, the final directory is created in octal 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.
dt touch [-XE] file ...dt touch myfileThe "upd" command touches the volume directory for the passed file or directory, so that all Macs that have mounted this volume can display the changes. This may be necessary e.g. if a file is created under UNIX and the Mac 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 if you can adjust your workflow to "dt" commands and thus avoid potentially harmful non-"dt" commands.
dt upd [-X] file ... | dir ...dt upd myfileNote: Mac clients only scan for changes every 10 seconds. Usually, folder information is 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 does 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 Mac flush its cache entries. Make sure that you are using the latest Mac OS and up-to-date AppleTalk/Network drivers.The "chmod" command changes the permission mode of a file. The mode may be absolute or symbolic.
dt chmod [-fRXy] absMode file ...dt chmod [-fRXy] [ugoa]{+|-|=}[rwxstugo] file ...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 spaces) of symbolic mode expressions of the form:
[who] operator [permissions]In order to adjust permissions for 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 444 file
sets only read permission (0444) to "file".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.
dt chown [-fhRXy] owner[:group] file ...-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.
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.
dt chown frank:support myfile
changes the owner for "myfile" to "frank", and the group to "support".dt chown 100 myfile
changes the owner for "myfile" to the user defined with the ID 100.Important: If the user specified with the "dt chown" command has never been validated by the HELIOS authentication server, it issues the "User not validated" error message. However, all regular UNIX users, e.g. "nobody", "root" are automatically validated.The "chgrp" command sets the group ID of a given file to that of the new group.
dt chgrp [-fhRXy] group file ...-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.
A group ID may either be specified by the numeric ID or by the corresponding group name.
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.
dt chgrp support myfile
changes the group to "support".dt chgrp 100 myfile
changes the group for myfile to the group defined with the ID 100.The main purpose of this command is problem detecting. The Mac file, or respective 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.
dt idinfo [-v volume] [-X] id ...Note: 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.dt idinfo -v /support 3159
prints the following information:volume: '/support' id=3159 pid=2 name: 'temp'
specifying the detected volume, 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.Each Mac file in 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".
dt iddump [-X] volumeThis command recursively descends the directory tree for each pathname listed, evaluating an expression in terms of each file in the tree.
dt find [-v volume] [-eiX] pattern ...8.11.2 Additional information
The information in this section is mainly meant for system administrators who want to integrate the "dt" tools into custom solutions, e.g. backup scripts. You do not need this information for the simple use of the "dt" tools (however, it does not hurt to read on).
Each HELIOS volume is accompanied by a corresponding desktop database, which holds additional information about each file or directory stored in this volume.
Each file, directory or stream in a HELIOS volume consists of two parts: the "data fork" and the "resource fork".
Though invisible to the Mac user, both parts of a file and the corresponding information in the desktop database are handled transparently and automatically by EtherShare. On Windows, a file consists of a long number of additional streams (but no desktop database info).
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, and handle the resources and streams.
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, and all corresponding streams.
You will find more information about this in "Directory and file formats" in the EtherShare manual.
Since UNIX files consist of only one part, but Mac files of two (see Mac 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 and streams.
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 and streams 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" tools do not require the desktop server to run on the UNIX server where you issue the commands, but by default the "dt" tools 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 Mac) the "dt" tools 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" tools are unable to connect to a desktop server, when the target directory is not mounted by any Mac and no local desktop server is running. In this case start a local desktop server or mount this volume on a Mac.
The "dt" tools 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 details.Double mounts (access to the same directory under different mount points, e.g.:
mount myserver:/usr/es /es
mount myserver:/usr/es /home/user1/es_copy)This will lead to differences between volume and desktop information, resulting in inconsistencies.
Please note that you may unintentionally cause this problem by accessing an already mounted volume via auto-mounter:
dt cp /net/myserver/usr/etherhare/file1 file2You may avoid this problem by running auto-mounter on any involved server (source and destination).
In 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 Mac.
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" tools 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.8.11.3 Using "dt" for backup/restore
One main purpose of the "dt" tools is to avoid problems when restoring data from a backup device. Here we describe how you should use the "dt" tools 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 Mac 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 you must 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 Mac 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.The HELIOS "dt" tools provide UNIX compatible file management to Windows. "dt" supports UTF-8 parameters and listings, and does not need a CLI to work.
Setting UNIX like file permissions ("owner", "group", "other", "mode") can be done from within "dt" and will be translated into Windows ACL permissions. Using "dt" tools within scripts has the advantage that Perl scripts will work on both Windows and UNIX platforms.8.12 rebuild
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.However, there is one particular situation where it may be required to use the "rebuild" program:
- 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 Mac, the resource file is deleted, too.)
So particularly if your HELIOS volume contains a mixture of Mac 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 19.6 "Rebuild preference keys").rebuild [-2cfnopsvxt] [-C oldes|utf8] [-U charset]
[-D charset] path_to_volume_rootThe following options can be used with "rebuild":
Disable 2 ID check passes (by default 2 ID check passes is active)
Do not clean resource orphans automatically (clean orphans is default if -c is not specified)
Force ".Desktop" file to be rebuilt (force create is off if -f is not specified)
Output to system messages file instead of "stdout"
Open ".Desktop" file only, repair if corrupted
Output the converted file names
Scan desktop only (scan is off if -s is not specified)
Verbose for diagnostics (verbose is off if -v is not specified)
Volume is exclusively opened for rebuilder
Print rebuild statistics every 10000 items
Convert volume file names from old EtherShare ":hex" to new "UTF-8"
Specify character set for a volume (e.g. PC850)
Change the output character set. The default is raw UTF-8
Force ".Desktop" file to be rebuilt:
rebuild -f /usr/local/helios/publicConvert volume file names from the old EtherShare to the new UTF-8 volume character set:
rebuild -C utf8 /data/my_testvolumeIn 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.
8.12.1 Preferences of the "rebuild" program
When it starts, the "rebuild" program first accesses the main configuration file "Preferences" to determine its configuration. 19.6 "Rebuild preference keys" lists the preferences, which can be changed if necessary by using the "prefvalue" command. See also 8.13 "prefvalue".
8.13 prefvalue
Setting and retrieving single entries in the preference database (see 19 "Preferences") can be done using the program "prefvalue" in "HELIOSDIR/bin".
To get the current value of a preference only, specify a key.
prefvalue -k '<key>' [-ld[r]] [-t type] [-p PreferenceFile] [-f valuefile||value]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!prefvalue -k 'Programs/pcshare/hostname'"prefvalue" is the command and -k the preference key (here
Programs/pcshare/hostname).Important: If the key comprises a path, the "/" characters within the path must be "marked" by preceding each with a "\" character.prefvalue -k 'Volumes/\/data1\/applications/AFPName'To set a preference value, specify key, type and value.
prefvalue -k '<key>' -t <type> <value>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).
To delete a preference, specify a key and the -d option.
prefvalue -k 'Programs/pcshare/hostname' -d"prefvalue" is the command, -k the preference key (here
Programs/pcshare/hostname), and -d the option to delete the preference.To delete a key with all its sub-preferences, specify the -r (recursive) option.
Important: Use this command with caution! Make a backup copy of "HELIOSDIR/var/conf/Preferences" first.To list all preferences of a key, specify the -l (list) option.
prefvalue -k 'Programs/pcshare' -lgatewaynameserverenableproxyenableproxyregcheckhostnamedomainnameprimarydomaincontrollerenablewinsofferNTCapsfilesextendedLog8.14 prefdump
Dumping preferences into a readable form can be done using the "prefdump" command in "HELIOSDIR/bin/".
prefdump [-o DumpFile] [PreferenceFile]prefdump -o 'HELIOSDIR/var/tmp/prefs.txt'"PreferenceFile" 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".
8.15 prefrestore
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".
prefrestore [-p PreferenceFile] [-c] [DumpFiles -]prefrestore 'HELIOSDIR/var/tmp/prefs.txt'"PreferenceFile" 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.
8.16 mail
"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 email 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)The following options can be used with "mail":
Sender address ("From:"). If the sender address is not given, the current user name is used.
Comma-separated list of recipients ("To:"). This parameter is mandatory.
Comma-separated list of additional recipients ("Cc:").
Comma-separated list of additional recipients whose addresses are not included in copies of the message ("Bcc:").
Address to which replies should be send ("Reply-To:").
Character encoding used in the mail message. The default is UTF-8.
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.If the option -m is not set, the preference SMTPHost (19.2 "Global preference keys") is used.
In addition, SMTPHost may also contain - apart from the actual address of the SMTP server - name and password for authentication:
name:password@Serveraddressmail -t user@domain.com -s 'Test subject' -b 'This is a mail test.'For longer mail messages it is easier to put the message text into a temporary file and send the message with
mail -t user@domain.com -s 'long test' < msgfileSend an email using an SMTP server requiring authentication:
mail -t user@domain.com -m "user:password@smtpserver.com"8.17 machid
A "machid" request from the command line delivers the machine ID from the host.
# cd /usr/local/helios/bin
# ./machid
cb5323c9-6c8.18 oiinfo
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.The program returns information about name and version of the respective plug-ins.
# /usr/local/helios/bin/oiinfoFound 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.With this option specified, information about all registered fonts are listed.
8.19 pstext
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 19.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.
pstext -f <Font> -s <Size> -h <Title> -e <PrepFile>
-L <LeftMargin> -T <TopMargin> -t <Tabsize>
-c <LineSpace> -o -l -m -n -p <Printer> file1 file2
-d <NewPrepFile>The following is an example of a typical command to print an ASCII file:
pstext -P lw .profileThis 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":
ls -l | pstext -P lwThe following example prints an entry from the UNIX manual:
nroff -man /usr/man/man1/ls.1 | pstext -P lwThe following options can be called with "pstext":
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.
Size of the font in points. The default is 10 points. One point is 1/72 inch.
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.
Print the date of the last modification to the file on the top line of each page, instead of the current date.
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.
Rotates the printed output by 90° (landscape mode printing).
Turns off the "pstext" escape interpreter. No characters are checked for control functions.
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").
Defines the desired line spacing in font height. The default is once the height of the used font.
Can be set to dump the internal "prep" file "pstext.ps" to a file for further editing and use it with the -e option.
8.19.1 Escape Interpreter
"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:
ESC 4 [10]or in hex: 1B 34 5B 31 30 5D
The following is a list of the supported escape sequences:
ESC 1 [1]
Underline on.ESC 1 [0]
Underline off.ESC 2 [1]
Bold printing on.ESC 2 [0]
Bold printing off.ESC 3 [Helvetica]
Choose a new font, in this example "Helvetica".ESC 3 [Courier]
Choose the standard font. "Courier" is the default font.ESC 4 [12.5]
Choose a new font size in points, in the example 12.5 points.ESC 5 [
gsave
newpath
50 50 moveto
80 80 lineto
closepath
stroke
grestore
]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".
ESC 6 [2]
Set line spacing (in this example to 2 times the font height).8.19.2 Umlauts and special characters
"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 HELIOS Base. 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:
% reencode font for DEC VT200 font
/decEncoding StandardEncoding dup length array copydup 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
defEach 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:
% we use the DEC encoding by default
/theEncoding decEncoding defIf you want to use IBM PC umlaut codes, change the above line as follows:
% we use the IBM encoding by default
/theEncoding ibmEncoding defYou 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.:
pstext -e myprep1.ps -P lw testfileThis command prints the file "testfile" using a new PostScript definition contained in the "prep" file "myprep1.ps".
8.20 start-helios
The "start-helios" command starts all available HELIOS services on the host (see 4.5 "Starting/Stopping HELIOS Services manually").
start-helios [-i]The following option can be called with "start-helios":
Initialize the HELIOS services during startup. If this option is specified before starting HELIOS, a re-installation will be done before starting the HELIOS services.
Note: The -i option will re-setup the HELIOS used Java and Perl versions. It will override any modifications in the HELIOS startup rc scripts and drivers with the original HELIOS versions.8.21 stop-helios
The "stop-helios" command stops all HELIOS services on the host 5 minutes after entering the command.
stop-helios [now] [-g] [-m]The following option can be called with "stop-helios":
Stops the services immediately.
Allows specifying the time until shutdown in minutes.
Allows issuing a shutdown message.
8.22 uwhat
The "uwhat" command displays the software version number of a HELIOS program.
Finding out the software version number of "swho":
cd /usr/local/helios/bin./uwhat swhoswho 1.6.3Or finding out the software version number of "afpsrv":
cd /usr/local/heliosbin/uwhat sbin/afpsrvsbin/afpsrv 4.0.08.23 lscom
This command lists all HELIOS COM (Common Object Model) plug-ins that have been loaded by the HELIOS server. It helps verify available COM plug-ins and to monitor their status.
Typical plug-ins which are loaded by the HELIOS server are:
lscom [-l]The following option can be called with "lscom":
Displayed plug-ins are additionally loaded. This may be helpful when troubleshooting or error tracking.
8.24 psyslog
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. "psyslog" will print all events since 0:00:00 of the current day unless it is overridden with the -d parameter.
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)The following options can be called with "psyslog":
<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.
Write the given process ID in brackets behind the tag.
Examples
Example 1:
psyslog -d '13.01.2005 12:00:00'List all entries in syslog files which are younger than "13.01.2005 12:00:00".
Example 2:
psyslog -fContinuously read syslog entries until "Ctrl-C" is issued. Output contains entries since "0:00:00" of the current day.
Example 3:
psyslog -d allPrint all entries found in log files.
Example 4:
psyslog -t myscript.pl Converting of image failedPost "myscript.pl: Converting of image failed" to syslog.
Note: On Windows there is no syslog service. Therefore Windows event logging is used.8.25 htar
"htar" is a HELIOS implementation of a UNIX tar file compatible archive program. It is designed to handle these features:
- Unicode UTF-8 file names
- Mac resource information
- Mac Finder information
- Mac OS 9 Finder information (Get Info)
- Creation date
- Restores folder modification date
- Supports Windows file streams
- Supports backup, archive, read-only and hidden attributes
- UNIX file permissions
- "Owner", "Group" and "Others" information
On Windows, file streams and SFM (Services for Macintosh) are used. "dir/file:stream:type" is stored in the archive as "dir/file" and "dir/.rsrc/file:stream:type". SFM Mac Resource/Finder information is converted into the ".rsrc" format while the creation date is preserved.
htar [-c|-t|-x] [-z|-Z] [-v] [-k] [m] [-b,-s blocksize] [-C <dir>] [-f <file>] [<file|dir> ...]
htar -h (for help info)The following options can be called with "htar":
Create archive from the given files and directories.
Test archive. "htar" tests the integrity of the entire archive.
Extract archive. "htar" extracts all files in a tar archive.
Create/read "gzip" compressed tar archive.
Create/read "compress" compressed tar archive.
Print file names when creating or extracting an archive, print detailed information on files when testing an archive.
Keep Mac 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 Mac files. Details are given at:
http://www.helios.de/news/news03/N_06_03.phtmlDo not memory map files and tar archives.
Change the tar archive read/write blocking factor, the default archive is 1MB blocking factor. Values can be specified in bytes, 512 byte blocks, kbyte or megabyte blocks, e.g:
-b 1024 (1024 bytes)
-b 10b (10*512 byte blocks)
-b 10k (10*1024 byte blocks)
-b 10m (10*1024*1024 byte blocks)Change the file read/write blocking factor, the default file
I/O is 1MB blocking factor. Values can be specified in bytes, 512 byte blocks, kbytes or megabytes blocks.Change to <dir> before creating/reading an archive.
Use tar archive in <file>. If this option is omitted or given as "-", "htar" reads from standard input (test/extract) or writes to standard output (create).
Create a gzip compressed archive:
htar -c -z -f backup.tgz file1,file2Extract the above created archive:
htar -x -v -z -f backup.tgzWindows: HELIOS tar archives internally use the UNIX notation with "/" rather than the Windows "\" notation. If "\" was used, the archive would not be recognized.8.26 printerlog
"printerlog" is a tool to list the "printer.acct" files in "HELIOSDIR/var/adm" in a human readable form.
printerlog [-p][-v][-h][-a|-1..7] print logfileThe following options can be called with "printerlog":
Repeat printing a headline every 60 entries.
Verbose output print all information recorded.
N can be a value between 1 and 7 which represents the log file "N" days ago.
Print out the current log file with all information:
# printerlog -vPrint out the log file 4 days ago, writing a headline every 60 entries:
# printerlog -p -48.27 serverlog
"serverlog" is a tool to browse the "server.acct" files in "HELIOSDIR/var/adm" in a human readable form.
serverlog [-p][-v][-h][-a|-1..7] print logfileThe following options can be called with "htar":
Repeat printing a headline every 60 entries.
N can be a value between 1 and 7 which represents the log file "N" days ago.
Print out the current log file:
serverlog8.28 HELIOS Windows tools
The following additional tools are available on a HELIOS Base for Windows installation.
8.28.1 kill
This tool resembles the UNIX "kill" command on Windows machines. It sends a signal to the HELIOS processes specified by the pid operands.
kill [-s signal] pid...
kill -signal pid...
kill -l [signal...]
kill -h help infoThe following options can be used with "kill":
A symbolic signal name specifying the signal to be sent instead of the default TERM.
A number or a symbolic name specifying the signal to be sent instead of the default TERM.
If no operand is given, list the signal names. Otherwise, for signal numbers write the signal names and vice versa.
kill -TERM pid Shutdown the processkill -HUP pid Reconfigure the processkill -KILL pid Kill the process without
shutdown8.28.2 ln
The "ln" tool resembles the UNIX "ln" command on Windows machines and creates a new directory entry which points to either a file or a directory that has the same modes as the original file.
ln [[-fsn]] <source_file> [<target_file> | <target_dir>]
ln -h help infoThe following options can be used with "ln":
If the target file exists, "ln" unlinks it first before creating the link.
If the target file or the target directory is a symbolic link, do not follow it (useful with -f).
Create "data" in the current working directory as a symbolic link to "F:\data":
ln -s F:\data dataCreate "myhardlink" as a hard link to "myfile":
ln myfile myhardlinkNote: Symbolic links created by "ln" use a special HELIOS format and are only recognized by HELIOS processes. Symbolic links are different from the Windows "Shortcuts".
Hard links created by "ln" are Windows NTFS hard links. They should only be used with extreme care.8.28.3 dd
HELIOS "dd" is a BSD-compatible "dd" tool which allows creating, copying, and splitting files. It can be used for benchmarking purposes, and serves as emulation of
"/dev/null" and "/dev/zero".The "dd" utility copies the standard input to the standard output. Input data is read and written in 512-byte blocks. If input reads are short, input from multiple reads are aggregated to form the output block. When finished, "dd" displays the number of complete and partial input and output blocks and truncated input records to the standard error output.
The following operands can be used with "dd":
Note: On Windows, no "dd" tape device functions are supported.Set both input and output block size to n bytes, superseding the ibs and obs operands. If no conversion values other than noerror, notrunc or sync are specified, then each input block is copied to the output as a single block without any aggregation of short blocks.
Set the conversion record size to n bytes. The conversion record size is required by the record oriented conversion values.
Copy n input files before terminating. This operand is only applicable when the input device is a tape.
Set the input block size to n bytes instead of the default 512.
Read input from file instead of the standard input.
Seek on the input file n blocks. This is synonymous with skip=n.
Set the output block size to n bytes instead of the default 512.
Write output to file instead of the standard output. Any regular output file is truncated unless the notrunc conversion value is specified. If an initial portion of the output file is seeked past (see the oseek operand), the output file is truncated at that point.
Seek on the output file n blocks. This is synonymous with seek=n.
Seek n blocks from the beginning of the output before copying. On non-tape devices, an lseek operation is used. Otherwise, existing blocks are read and the data discarded. If the user does not have read permission for the tape, it is positioned using the tape ioctl function calls. If the seek operation is past the end of file, space from the current end of file to the specified offset is filled with blocks of NUL bytes.
Skip n blocks from the beginning of the input before copying. On input which supports seeks, an lseek operation is used. Otherwise, input data is read and discarded. For pipes, the correct number of bytes is read. For all other devices, the correct number of blocks is read without distinguishing between a partial or complete block being read.
Display the HELIOS "dd" version number.
Where <value> can be one of the following parameters:
dd conv=<value_1>,<value_2>,<...>Do not stop processing on an input error. When an input error occurs, a diagnostic message followed by the current input and output block counts will be written to the standard error output in the same format as the standard completion message. If the sync conversion is also specified, any missing input data will be replaced with NUL bytes (or with spaces if a block oriented conversion value was specified) and processed as a normal input buffer. If the sync conversion is not specified, the input block is omitted from the output.
On input files which are not tapes or pipes, the file offset will be positioned past the block in which the error occurred using lseek.
Do not truncate the output file. This will preserve any blocks in the output file not explicitly written by "dd". The notrunc value is not supported for tapes.
Pad the final output block to the full output block size. If the input file is not a multiple of the output block size after conversion, this conversion forces the final output block to be the same size as preceding blocks for use on devices that require regularly sized blocks to be written. This option is incompatible with use of the bs=n block size specification.
If one or more output blocks would consist solely of NUL bytes, try to seek the output file by the required space instead of filling them with NULs, resulting in a sparse file.
Pad every input block to the input buffer size. Spaces are used for pad bytes if a block oriented conversion value is specified, otherwise NUL bytes are used.
Treats the input as a sequence of fixed length records independent of input and output block boundaries. The length of the input records is specified by the cbs operand. Any trailing space characters are discarded and a newline character is appended.
Where sizes are specified, a decimal, octal, or hexadecimal number of bytes is expected. If the number ends with a "b", "k", "m", "g", or "w", the number is multiplied by 512, 1024 (1K), 1048576 (1M), 1073741824 (1G) or the number of bytes in an integer, respectively. Two or more numbers may be separated by an "x" to indicate a product.
When finished, "dd" displays the number of complete and partial input and output blocks, truncated input records and odd-length byte-swapping blocks to the standard error output. A partial input block is one where less than the input block size was read. A partial output block is one where less than the output block size was written. Partial output blocks to tape devices are considered fatal errors. Otherwise, the rest of the block will be written. Partial output blocks to character devices will produce a warning message. A truncated input block is one where a variable length record oriented conversion value was specified and the input line was too long to fit in the conversion record or was not newline terminated.
Normally, data resulting from input or conversion or both are aggregated into output blocks of the specified size. After the end of input is reached, any remaining output is written as a block. This means that the final output block may be shorter than the output block size.
The "dd" utility exits "0" on success, and ">0" if an error occurs.
Copy file with a block size of 512 bytes:
dd if=input_file of=output_file bs=512Create 100 MB file with 100 blocks of 1024 KB:
dd if=/dev/zero bs=1024k count=100 of=output_fileRead 100 MB file with a block size of 1024 kB:
dd if=input_file of=/dev/null bs=1024k8.28.4 crontool
This tool is used to add scheduled jobs on Windows machines to the Windows Scheduled Tasks menu (Start > Control Panel > Scheduled Tasks). It can start and stop specified programs at midnight.
Usage (in the "HELIOSDIR\sbin" directory):
crontool [-i <command>] [-u <command>] [-l]The following options can be used with "crontool":
Schedule job to run at a specified time each day.
Remove job from the list of scheduled commands.
Print the list of scheduled commands. Another way to print this list is with the Windows "at" command.
Schedule "C:\Program Files\My Company\mycronjob.bat" to run at 00:00 each day:
crontool -i "/C:/Program Files/My Company/mycronjob.bat"Remove the above job from the list of scheduled commands:
crontool -u "mycronjob.bat"Note: A simpler way to execute daily jobs is to place a Perl script into the "HELIOSDIR\etc\daily" folder.8.28.5 Windows printing to HELIOS queues
Note: The following description is only for HELIOS Base services running on Windows.Mac OS X uses the PAP or TCP printing system, UNIX systems use Remote LPR. Windows printing is based on SMB/CIFS. HELIOS print monitor manages forwarding SMB/CIFS print jobs into the HELIOS printing system. During the HELIOS software installation it is automatically installed into the Windows system. The necessary driver is described in the Driver section below.
Creating a Windows printer that prints to a HELIOS queue:
Go to Start > Printers and Faxes > Add a printer.
Select Local printer attached to this computer and click the Next > button. From the Use the following port pop-up menu select a HELIOS queue (Fig. 89).
Important: The selected printer must be marked as (HELIOS Queue), compare pull-down menu entries in Fig. 89)!Select the printer manufacturer and model from the lists and click Next >.
As proposed by the wizard, you should keep the already existing printer driver. Otherwise you must specify a new printer driver later. Click Next >.
Name the printer and specify whether you want to make the printer the default printer. Click Next >.
Select printer sharing and specify a printer share name, or just accept the proposed name (for shared printer names, Windows only allows up to 8 characters). Click Next >.
You may optionally enter information on the printer location (e.g. "HELIOS_Windows") and comments. Click Next >.
Specify if you wish to print a test page (e.g. to verify the HELIOS print monitor installation). Click Next >.
The "Add Printer Wizard" gives you a summary of the printer settings. Click Finish to complete the installation.
Now the new printer appears in the Printers and Faxes window (Fig. 90).
During the HELIOS software installation, via the command "start-helios -i", the HELIOS print monitor driver "HELIOSPrinterMon_s.dll" (or "HELIOSPrinterMon64_s.dll" - depending on the architecture) is copied from "HELIOSDIR\etc\printmon" into the "WINDOWS\system32" folder.
Note: Sometimes the driver is busy in the Windows folder so that updating the "HELIOSPrinterMon_s.dll" does not work. Reboot, then try again.8.29 Third-party Windows tools
8.29.1 Sysinternals tools for Windows
There are two monitoring tools by Sysinternals that are recommended for using HELIOS products on a Windows platform: "Process Monitor" and "Process Explorer".
For installation and use of the tools, please see the Sysinternals website (www.sysinternals.com).
Process Explorer shows information about which handles and DLLs processes have opened or loaded.
The Process Explorer display consists of two sub-windows. One window always shows a list of the currently active processes, including the names of their owning accounts, whereas the information displayed in the other window depends on the mode that Process Explorer is in: handle mode or DLL mode. Process Explorer also has a powerful search capability that will quickly show which processes have particular handles opened or DLLs loaded.
Process Monitor is an monitoring tool for Windows that shows real-time file system, Registry and process/thread activity. It combines the features of two legacy Sysinternals utilities, "FileMon" and "RegMon", and adds an extensive list of enhancements including rich and non-destructive filtering, comprehensive event properties such session IDs and user names, reliable process information, full thread stacks with integrated symbol support for each operation, simultaneous logging to a file, and much more.
8.29.2 Wireshark Network Analyzer
Wireshark (formerly known as "Ethereal") is used by network professionals around the world for troubleshooting analysis, software and protocol development, and education.
For installation and use of the tools, please see the Wireshark website (www.wireshark.org).
| © 2008 HELIOS Software GmbH |
|
|
|
|
|
