On Fri, Oct 27, 2000 at 11:28:52AM +0200, Robin Sommer wrote:
> after an upgrade from LPRng 3.6.22 to 3.6.26 at least two of our
> users have problems. They get an error message like
>
> Max_open:fd 34 and old Max_fd 19
>
> when they print from specific applications (ghostview and Acrobat
> Reader). Looking into the source it seems that this error message
> hasn't been in 3.6.22. What is it supposed to mean and what can we
> do about it? Any idea?
Apparently those applications start the sub-process with many file
descriptors assigned (they fail to close the files or use FD_CLOEXEC),
and this confuses the Max_open function, which tries to sanity-check
new fd's. As a work-around, just replace 10 by something
bigger (such as 100) in child.c. The solution would be to have
lpr close unneeded file descriptors in main().
--
Bodo M�ller <[EMAIL PROTECTED]>
PGP http://www.informatik.tu-darmstadt.de/TI/Mitarbeiter/moeller/0x36d2c658.html
* TU Darmstadt, Theoretische Informatik, Alexanderstr. 10, D-64283 Darmstadt
* Tel. +49-6151-16-6628, Fax +49-6151-16-6036
-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
