HELIOS EtherShare 2.6 User manual
HELIOS offers a variety of support options to help you get the most from HELIOS products. This section summarizes those options.
If you have any questions about your HELIOS product, first read the printed documentation. Also consult the README files, which may have been provided with the product to describe late news which are not covered by the main manual. Last but not least, you may check our Web site regularly:
If you still cannot find the answer to your question, your first line of support is your HELIOS product supplier or dealer. Please have the following information at hand:
- Did you try to get help from one of our dealers or distributors? Please let us know if you found your dealer to be little helpful and/or lacking in experience.
- The serial number of your HELIOS product (this is printed on your "Activation Key Request" form. Alternatively, the machine ID of your computer (see What you have to do in chapter "Welcome to EtherShare 2.6").
- Your full address, telephone/fax number, and e-mail address, if available.
- HELIOS partner contact: name, e-mail address, fax, phone.
- For every EtherShare/PCShare server at your site:
- UNIX: information about the hardware and operating system
- The version of all relevant HELIOS software modules (see chapter 5.13.6 "Versions") and the name and version of any Macintosh application software (such as DTP programs) or INITs you were using at the time.
- Details about your EtherShare configuration file "atalk.conf". For printer-related queries, we will need details of your "/etc/printcap" file, too.
- The type of hardware you are using and the operating system version (use the "uname" command ( with an appropriate parameter e.g. uname -a to find out).
- The exact wording of any messages that appeared on your screen, and details of relevant messages in the following files:
- What happened and what were you trying to do at the time the problem occurred?
- How did you try to solve the problem? Contents of "/etc/passwd", "yp/passwd" (we are only interested in the location of users' home directories)
- Output of "/etc/(v)fstab", "exports"
- Output of "find / -name .afpvolumes -print",
"find / -name .Desktop -print"
- "rebuild -s" for every EtherShare volume
- In case any changes have been made to your initial EtherShare/PCShare configuration, we need the contents of the current configuration files.
- Send the exact and complete command sequences you issued together with the exact and complete output produced by the "dt" utilities and/or other UNIX programs you have used. (If you can use a scrollable command window, e.g. within XWindows, OpenWindows, CDE, or similar tools, this will facilitate the task of providing this information, especially since the history of earlier command sequences is also available in this window!)
- Let us have the output of "ls -la" for the directory where you applied the "dt" command, as well as for the corresponding ".rsrc" directory. In case you applied a change recursively, you can simply use
- If you used a "dt" command which processes a source and destination file/folder, please submit all the information for both, source and destination.
- Let us have the output of "ps -efl", or "ps aux", respectively.
- Let us have the output of "$ESDIR/swho -c" and "$PCDIR/swho -c".
- Let us have the output of "df".
- Specify the contents of the system messages files since the last start of EtherShare.
- Let us have a description of what you wanted to achieve, and what - you think - has happened.
- Is the result reproducible or does it emerge only occasionally? Any clue on the suspected pattern will be helpful!
- In case you have additional information available, e.g. core files, trace output, please store it safely and make a note in your report - do only send it on request.Depending on the severity of the problem it may be necessary to stop and start EtherShare services completely. If you use shared volumes together with PCShare, stop PCShare first, and restart it only after restarting EtherShare.
If the dealer cannot solve the problem, he or she can contact the official HELIOS distributor in your country. HELIOS has appointed distributors in about 20 countries - you can find their addresses on HELIOS product brochures or on the HELIOS Web site www.helios.de. Each distributor and HELIOS OEM customer is obliged by contract to have technical support staff who are experienced with HELIOS products.
Note: The current HELIOS CD-ROM provides a support questionnaire called "es_quest.pdf" which helps you have all important information at hand when contacting the HELIOS product supplier or dealer.All HELIOS products require an Activation Key (or password) to be entered during (or after) the installation. Without the Activation Key, the software cannot be started. End-user Activation Keys are dependent on the machine ID of the host and the EtherShare serial number. The installation program will let you know your machine ID automatically.
Note: If we generate a key twice for the same combination of machine ID and EtherShare serial number, the second key may be different from the first one. This is normal.At their discretion, HELIOS distributors can provide their dealers - for a reduced fee - with so-called dealer demonstration versions of our products, which are fully working copies of our software but carry a special Activation Key which expires after a given period of time. You will be informed about the time remaining on your demonstration copy by a "afpsrv" message which pops up each time you log on to the File Server, and then each 3 - 4 hours while being logged-on to the File Server (see figure 159):
Fig. 159: Demonstration key warning
If you are transferring your EtherShare software from one host to another, then we call this an "Activation Key Transfer". When you apply for a new key, you will need to state that you will no longer use EtherShare (and depending EtherShare OPI, PDF Handshake, Print Preview, or user expansion licenses) on the original host - fax our key registration department (+49-5131-70 93 25) and ask for details of the exact wording to use and the conditions that apply.
Note: If you do not enter any Activation Key the HELIOS product you have installed will run in a 3 hour demo mode only.HELIOS releases new versions of its software products from time to time, for example to make improvements or to correct known faults. HELIOS distributors and OEM customers automatically receive the latest version in new shipments.
An automatic software update service ("Software Update Service Agreement") is available for endusers who wish to receive new major product versions and intermediate product releases automatically. This is implemented by shipping a single CD-ROM containing the latest versions of all of our products. The CD-ROM will be produced whenever a significant new product version is released.
Customers not taking part in the update service will only receive replacement software modules if their installation does not function according to the claims made by HELIOS at the time of purchase. For example, if Apple upgrades its printer driver and this causes a problem with one of our products, the solution to the problem will only be made available to customers with a service contract. Other customers can still upgrade their software when new major releases become available, by paying the appropriate upgrade fee. HELIOS will inform all customers who do not have an update service contract about fees for upgrading existing installations as soon as new releases become available.
Another way to obtain the latest HELIOS software updates is called "Internet Update Access", which provides the customer with the latest updates via HELIOS Web site.
For both update service products contact your supplier for price information and for a copy of the relevant application form, or visit the HELIOS Web site: www.helios.de.
The following section lists and describes the most important error messages for all UNIX program modules except for the Desktop Server. Desktop Server errors are described in the corresponding chapter.
All error messages are constructed the same way. They start with the name of the issuing program followed by the UNIX process ID [in brackets]. This is then followed by a verbose error message which may include variable strings and numbers, for example:
In the following, strings are abbreviated by "%s", numbers by "%d" and UNIX system error messages by "%m". Refer to your UNIX documentation for more information on UNIX system error messages.
All EtherShare servers verify the integrity of the executable image by performing a checksum and verify the license by reading the license file "$ESDIR/conf/ethershare.license".
The program checksum did not match. A common reason is that you have transferred your EtherShare installation via FTP and you have forgotten to set FTP to image (binary) mode.
EtherShare demo versions run for a limited time, and the license has now expired. Each user is warned at every login to the File Server that he is using a demo version, and also for how many days the license will still be valid. Thus, the expiry should not take effect surprisingly. See Demonstration keys in chapter 17.2 "Keys and updates".
The "Checksum" field in the license does not match the data in the other fields. This should not happen as the installation procedure verifies that a license is valid before entering it into the license file. However, this error message may appear e.g. if you have upgraded from EtherShare 2.2 to EtherShare 2.6 but still use the old key, or when you installed another version of the product to another directory and the data mix up.
The "MachID" field of the license does not match the host's machine ID. This might happen if you transfer a complete installation to a new host or if you get a new machine due to a hardware replacement. Contact our license department for a license transfer (see Activation Key Transfers in chapter 17.2 "Keys and updates").
The user expansion license did not find the proper base serial number. Verify that you have specified the proper base serial number when requesting the user expansion license from our license department.
Various error messages from system calls are logged-in this form. "syscall" is one of the common system calls (fork, malloc...) and "%m" gives the reason why the call failed. Common reasons like "No more processes" or "Not enough core" point to resource shortages, such as "not enough swap space", or "process table too small". Refer to your UNIX documentation for more details.
The AppleTalk toolkit could not be initialized. This happens if "atalkd" is not running or not a single known interface could be activated. This situation is usually preceded by messages from "atalkd". The message can also start with "ATPLoad" or "OpenXPP" rather than "MPPOpen".
The server in question could not register its name on the network. If "%s" = "Duplicate name exists already", this indicates that the AppleTalk name of the specified EtherShare server is already in use. EtherShare servers by default use the UNIX host name, but you can stop EtherShare on the server in question and rename it using the "name=" parameter in "atalk.conf".
"atalkd" is the first program started by "start-atalk", and is responsible for configuring the network interfaces. Thus, most of the error messages are concerned with network errors. All error messages are prefixed with "atalkd:". This is left out in the following for brevity. "atalkd" can also issue any of the error messages listed above under 17.3.1 ""license" error messages" and 17.3.2 ""generic" error messages".
Some error messages depend on the class of operating system (OS). "atalkd" divides the variations in two classes: streams-based OS (e.g. Solaris 2.x) and socket-based OS (SGI, RS/6000...).
"atalkd" could not open the DDP streams multiplexor. This will happen if the kernel modules are not installed (streams-based OS only).
An error occurred while opening an AppleTalk socket. The first "%s" is the socket (rtmp, nbp...) and the second "%s" is the error cause. The most likely reason is that an attempt was made to start a second "atalkd" process while one is already running.
"atalkd" could not understand the syntax of the "if=%s" entry in "atalk.conf". Use "netconf" (in "$ESDIR") for network configurations instead.
The interface "%s" could not be opened due to "%m". You will get this error e.g. if you specify a non-existent interface in the "if=" parameter in "atalk.conf" (streams-based OS only).
With a streams-based OS, you will get this error if you specify an interface unit number which is not supported by the underlying network driver (e.g. "le2" if you have only "le0" and "le1").
With a streams-based OS, this can happen if the specified service access point is already in use. For example, this could happen if you start "atalkd" twice or if you have another product installed that already uses AppleTalk.
The interface "%s" was supposed to be configured automatically, but no external seed router was found to supply network numbers and zone names. For example, more than one interface card is installed on your server and none of the network segments has an active seed router.
The interface "%s" was configured with a network number range that conflicts with other network interfaces. Use the "autoconf" option in "netconf" (in "$ESDIR") to let "atalkd" automatically configure the interface.
The interface "%s" was configured manually to use a particular network range, but an external seed router did supply a different range for this cable segment. "atalkd" will use the value from the external seed router and ignore the manual configuration.
While the network was already up and running a new router on network interface "%s" was sending conflicting routing table information. The conflicting information will be ignored. This can happen if a router starts up later (e.g. on a dialup line) or two previously independent AppleTalk networks are merged. All routers that seed that cable segment must be checked for proper configuration.
The routing information received on interface "%s" shows that the maximum hop count of AppleTalk packets would be exceeded attempting to reach network "%d". Check your AppleTalk network topology in order to provide no network is more than 15 hops away from any other part of the network.
With a socket-based OS, "atalkd" could not create an AppleTalk socket. If "%m" = "Protocol not supported", this means that no AppleTalk kernel modules are found in the currently running UNIX. If "%m" = "Can't assign requested address", this means that none of the network interfaces specified in "atalk.conf" succeeded to configure.
"atalkd" could not get the flags associated with interface "%s". This can happen if the interface specified in the "if=" parameter in "atalk.conf" does not exist (socket-based OS only).
"atalkd" could not set the AppleTalk address for an interface. This happens on all interface cards that do not support AppleTalk.
The named routine (nbp, rtmp...) could not write a packet to network "%d". If "%s" = "Network unreachable", this usually means that network numbers are misconfigured.
A route could not be added by "atalkd" to the kernel-resident routing table. This usually means that network numbers are misconfigured.
"atalkd" could not add a multicast address (functional address on Token Ring) for interface "%s". This can happen if there are too many zones configured for one Phase II network, or if the hardware interface does not support multicast addresses.
"atalkd" could not register its serial number on the network. This can happen if you use the same enduser serial number twice on the network, e.g. you have transferred EtherShare to a new host and not deleted the old copy.
"atalkd"has detected that there is another end user copy of EtherShare on the network which is using the same serial number.
Note: The following "atalkd" error message can only occur with EtherShare 2.6 under Linux:With a socket-based OS, "atalkd" can only configure one network interface automatically. All following interfaces are ignored. See appendix A 3.3 "Network automatic configuration option" for more details.
"afpsrv" can issue any of the error messages listed above under 17.3.1 ""license" error messages" and 17.3.2 ""generic" error messages", as well as a few messages related to the communication with "opisrv" and "desksrv" and the "Shared Memory" segment used to hold the file and record locking table.
The "maxfiles=" parameter specified more open files per process than the current system configuration allows.
"afpsrv" could not open the "Shared Memory" file "%s" ("$ESDIR/locktable") after forking for a new login. If this file is removed, no one can log in until the next restart of "afpsrv".
The number of record locks issued by clients exceeds the number configured by the "locks=" parameter.
"afpsrv" could not bind its event listener socket. If the reason is "Address already in use" then this is due to a second master "afpsrv" process running on the same machine.
"afpsrv" could not parse file "%s" ("$ESDIR/conf/
suffixes") in line "%d". This might happen if you edit the "suffixes" fileby hand instead of using the EtherShare Admin.
Added additional error messages for "afpsrv" to indicate potential problems due to corrupted "Shared Memory" segments:
afpsrv slave process <ID> was killed by signal <signal>, use stop-atalk followed by start-atalk to ensure integrity of shared memory segments
This message can occur on all currently supported platforms and indicates that "afpsrv" slave processes were intentionally killed by a UNIX user.
"afpsrv" will try 6 times for 5 seconds each to reach the desktop server to retrieve or store information from/to the desktop database of its volumes. Earlier versions of "afpsrv" tried 3 times for 5 seconds. Although even the older values were a very long time for network or RPC connections, we decided to even extend these values.
If "afpsrv" does not get a response from "desksrv" within this period of time this indicates a severe problem with the underlying UNIX operating system, UNIX file system or RAID/HSM drivers, or a hardware problem related to SCSI or hard disks.
To prevent inconsistencies between information stored in the desktop databases of an EtherShare volume and the files/folders on this volume, the "afpsrv" client process encountering this time-out will secure this volume (all mounted volumes) against write access. Opening folders and reading files will still be possible, but creating/renaming/ moving files or folders will not be possible any longer. Not even trashing files/folders will be allowed.
Apart from the usual messages issued in the UNIX system error log, this message will also be sent to the Macintosh client whose "afpsrv" server process encountered the problem. For more information on the Macintosh client messages refer toafpmsg in chapter 9.4 "Parameters of the "afpsrv" program".
Since applications usually work with temporary files/folders, it may not be possible to save single files. If this problem was only temporary, unmounting all EtherShare volumes and remounting them will make these volumes writable again. If instead, this was no temporary problem and is not solved in the meantime the Macintosh volume Chooser will list all volumes grayed out, and no volume will be mountable. Not even root will be able to mount any of these volumes.
Note: Each time such an error message occurs, EtherShare has to be restarted by entering "stop-atalk" and "start-atalk" respectively, otherwise the File Server is prone to improper operation."afpsrv" will now issue error messages on the client if the communication to "desksrv" fails and the volume falls back to read-only access. The message is:
Under certain conditions, an additional error message is issued and the volume is unmounted automatically by the Finder.
Though this message is issued by one "afpsrv" client process only, it is likely that all other "afpsrv" processes may encounter the same problem and therefore, the UNIX system administrator should be notified immediately.
"afpsrv" could not lock the "Shared Memory" segment file "locktable". This might happen if the file was removed using the UNIX command "rm".
"papsrv" can issue any of the error messages listed above under 17.3.1 ""license" error messages" and 17.3.2 ""generic" error messages", as well as a few messages related to the spooling system and to the communication with the client.
"papsrv" could not register its name on the network. This is because the name in the Chooser specified by "name=" in "atalk.conf" is already being used by another printer or spooler on the network.
"papsrv" could not change its current directory to the spool directory. Check if the directory specified in the printcap entry really exists and the spelling is correct.
"papsrv" cannot scan the "dicts" directory for PostScript dictionaries. Check that the "$ESDIR/dicts" directory exists or the "dictdir=" parameter in "atalk.conf" points to the appropriate directory.
If "%s" is an argument to a "filtercmd=" parameter specified in "atalk.conf", then it could not be executed. Check the syntax, it has to be a valid shell command.
"papsrv" could not execute the program "%s". This program may be an argument to a "filter=" or "lpr=" parameters in "atalk.conf".
"papsrv" could not open the temporary spool file in the spool directory. Check the free space (blocks and inodes) on the disk containing the spool directory.
"termsrv", "mailsrv" and "admsrv" can issue any of the error messages listed above under 17.3.1 ""license" error messages" and 17.3.2 ""generic" error messages". There are only a few other commonly encountered error messages from "mailsrv".
A more detailed description of the Mail Server parameters and their default settings are described in chapter 14.3 "Parameters of the "mailsrv" program".
Since, under EtherShare, printer interface programs are referenced by the logical (UNIX) printer name rather than their real name (such as "papif" or "tcpif") it is neccessary to look up the real program name in the "if" directory as described in chapter 11 "The Print Server". The following section describes errors using the real program names.
A temporary file name for saving error output until the real error message file has been established could not be determined. System call failure.
The temporary file "%s" for saving error output until the real error message file has been established could not be created. System call failure.
None of the locations (directories) of the HELIOS products were found. "%s" is an explanatory error message.
The HELIOS EtherShare product location (directory) could not be found. Mostly an installation error.
The message string handling for the message block "%s" could not be initialized. "%s" is an explanatory error message.
The printer has an entry in the "/etc/printcap" file but lacks the information about its spool directory.
The following messages may appear while retrieving information from a printer's PPD file. They mostly occur because of bad, misformed or damaged PPD files:
A fatal error occured while restarting the line printer daemon. Mostly a UNIX system failure caused by a lack of system resources or an already running "lpd".
The current print job does not have an control file. This may occur in case a printer interface program is started manually and not by the "lpd".
The current print job should have a history entry in its control file but none is found. This occurs with damaged control files either created while the system was out of resources or manipulated manually.
The line printer daemon process issued the output "%s" while starting or handling requests. This output normally is an error message and indicates a serious problem of the "lpd" system.
The filename "%s" could not be parsed into its key and path parts. This indicates a configuration error of a preference value.
The file "%s" could not be opened. This indicates an access problem either because the file does not exist or there are not enough privileges to open the file.
No information could be gathered for printer queue "%s". This indicates a configuration error. "%s" is an explanatory error message.
The status of the printer queue "%s" could not be determined. This indicates a configuration error. "%s" is an explanatory error message.
The control file of the current print job cannot be read. This indicates a damaged or missing control file. "%s" is an explanatory error message.
The modified print job's control file could not be written. This indicates a UNIX system call failure. "%s" is an explanatory error message.
The job history file entry could not be appended to a job's control file. "%s" is an explanatory error message.
The HELIOS resource "%s" could not be found. This indicates a corrupted program file. "%s" is an explanatory error message.
The status of the hold queue for the current job's printer queue could not be queried. "%s" is an explanatory error message.
The current print job could not be copied to the hold queue after job completion. "%s" is an explanatory error message.
The hold queue could not be restarted after a job had been copied. "%s" is an explanatory error message.
The status of the error queue for the current job's printer queue could not be queried. "%s" is an explanatory error message.
The status of printer the queue for the current job could not be queried. "%s" is an explanatory error message.
The status of the printer queue for the current job could not be changed. "%s" is an explanatory error message.
The current print job could not be copied to the error queue after job completion. "%s" is an explanatory error message.
The error queue could not be restarted after a job had been copied. "%s" is an explanatory error message.
An error occured while writing to the EtherShare printer accounting file. This is mostly due to a UNIX system call failure in case no space is left on the disk.
A printer interface program could not send mail to a print job's originator because the originator is unknown.
A printer interface program could not find the required program for delivering mail to a print job's originator. This is mostly caused by an inappropriate system installation.
A printer interface program could not start the required program for delivering mail to a print job's originator. This is mostly caused by an inappropriate system installation.
A UNIX system call failed while piping data to the mailer program. This is mostly caused by an unexpected abortion of the mailer program due to e.g. a lack of resources.
The OpenImage library could not be initialized. This mostly happens in case EtherShare has not started correctly. More error output follows after this text.
The required procset "%s" could not be included into the PostScript print jobs due to a UNIX system call failure.
The required font "%s" could not be found and the option "checkfonts" is switched on. Therefore printing is aborted.
The required font "%s" could not be found and the option "checkfonts" is switched off. Therefore printing is continued.
The required procset "%s" version "%s" revision "%s" could not be found. This error is ignored due to real world programs which mostly generate wrong procset references which can be ignored without messing up the print job.
An error occured while moving font information between internal lists. "%s" is an explanatory error message.
A fatal error occured while initializing a printer interface program. This error will be a persistent system failure and would cause the following print jobs also to fail. Therefore the printer queue has been stopped until the cause of the failure has been eliminated. The queue has to be restarted manually by using the EtherShare Admin.
An internal execution operation failed. This mostly occurs in case the system is low on virtual memory. More error output follows after this text.
The execution of the DSC comment "%s" failed. The print job does continue printing but the result may not be as expected.
An error occured while reading from a PostScript data stream. Mostly an explanatory error message follows.
An error occured while registering font information in internal lists. "%s" is an explanatory error message.
The job history file reference in the control file of the current print job is required but missing or damaged.
The parameter "%s" is missing in file "%s".
The list of balanced queues is empty.
An error occured while copying a job from the balance queue to the balanced queue "%s". "%s" is an explanatory error message.
The balanced queue "%s" could not be restarted. "%s" is an explanatory error message.
A UNIX system called failed while renaming file "%s" to "%s".
The configured notify program "%s" is neither an executable program nor a named pipe.
The notify program could not be started due to a UNIX system call failure.
Information about the file "%s" could not be gathered due to a UNIX system call failure.
The file "%s" must be a UNIX directory.
The file "%s" could not be created due to a UNIX system call failure.
The "diskif" program could not write data to the file "%s" due to a UNIX system call failure.
An error occured while resolving the PostScript print job. Mostly more error messages follow this text.
A read UNIX system call failed.
A UNIX system call failed while copying the PostScript print job to the file "%s".
A UNIX system call failed while flushing and closing the PostScript output file.
A UNIX system call failed while piping PostScript data to an executable program or named pipe "%s".
The configured directory for placing resolved PostScript print jobs is in an unknown notation and cannot be converted to a UNIX filename.
The file "%s" could not be locked for exclusive access.
The requested compression method could not be created.
The disk space went low while creating the PostScript output file. In this case the "diskif" program stops and waits until more disk space is available.
The "diskif" returned to normal operation after waiting for disk space to become available.
Extraction of the AppleTalk address obtained from an NBP lookup failed. "%s" is an explanatory error message.
Initiating open of a PAP connection failed. "%s" is an explanatory error message. It can also appear if AppleTalk sockets are exhausted.
An AppleTalk error occured while trying to open the PAP connection. "%s" is an explanatory error message.
The PAP printer "%s" could not be found on the network. Mostly this indicates that the printer is switched off.
An error occured while loading an AppleTalk protocol module. "%s" is an explanatory error message.
An error occurred during "establish read data" from a PAP connected printer. "%s" is an explanatory error message.
An error occurred during "establish write data" to a PAP connected printer. "%s" is an explanatory error message.
An error occured while reading data from a PAP connected printer was in progress. "%s" is an explanatory error message.
An error occured while writing data to a PAP connected printer was in progress. "%s" is an explanatory error message.
An error occured while retrieving network address of a PAP connected printer. "%s" is an explanatory error message.
An error occured while gathering status information from a PAP connected printer. "%s" is an explanatory error message.
A UNIX system call failed while creating a file stream from a string buffer.
A UNIX system call failed while setting the serial line into a non-blocking mode.
The printer cannot be accessed.
A UNIX system call failed while writing data to a serially connected printer.
A UNIX system call failed while reading data from a serially connected printer.
A illegal or wrong option was given or an argument is missing while running the "psresolve" program from the command line.
A UNIX system call failed while writing the resolved PostScript data to disk. This indicates mostly that there is not enough disk space available.A UNIX system call failed while retrieving information about the maximum size for a write operation.
A UNIX system call failed while signaling EOF to the "Shared Memory" printer.
A UNIX system call failed while signaling an interrupt to the "Shared Memory" printer.
A UNIX system call failed while accessing the "Shared Memory" buffer space.
A UNIX system call failed while reading data from the "Shared Memory" printer.
A UNIX system call failed while reading status messages from the "Shared Memory" printer.The TCP/IP protocol is missing in the UNIX system databases. Please check your UNIX network configuration.
The host with name "%s" is missing in the UNIX "/etc/hosts" database. Please check your UNIX network configuration.
The service "%s" specified in the UNIX "/etc/services" database is missing, or the service is not supported in conjunction with protocol "%s". Please check your UNIX network configuration.
Cannot connect to the TCP/IP internetworked printer. This indicates the failure of a UNIX system call.
The connection to the "Remote LPR" "%s" is broken. This might be caused by a crash of host "%s".
Connecting to a remote "lpd" on host "%s" failed. "%s" is an explanatory error message.
A UNIX system call failed while reading data from a TCP/IP connected printer.
A UNIX system call failed while setting the TCPI/IP connection into non-blocking mode.
A temporary file used for storing resolved PostScript data could not be created.
A UNIX system call failed while writing data to a temporary file.
A UNIX system call failed while copying PostScript data from a temporary stream into the output stream.
A UNIX system call failed while writing PostScript data into the output stream.
Lost TCP/IP connection while talking to printer "%s" on host "%s".
A recently created file cannot be accessed anymore.
The "lpd" on the remote system signals that its queue has no disk space left to store the print job.The "Remote LPR" printer "%s" will not accept a print job any longer because the remote queues are overfilled.
The transfer of file "%s" to a "Remote LPR" failed because the local and transferred size of the file differ.
|© 2002 HELIOS Software GmbH|