| - stop/start LPD : no change
- reboot cluster : no change
- tried to replace ucx$lpd_smb and ucx$lpd_shr with 4.1 plain versions
failed for unclear reason. now nothing works at all in LPD.
- tired, fed up, wanna go home--> instal original 4.1 ECO 4 images again
- stop/start lpd: all works fine again.
I would appreciate to get some advice for breakfast tomorrow.
Erwin
|
| Hi,
The problem came back, and we found the cause but do not understand
entirely the mechanism:
Here is the mechanism:
1) LPD client sends .cf and .df file to LPD server.
.cf file contains, among other info, the name of the client.
LPD client has an entry for LPD server in host database.
2) LPD client (ucx$lpd_queue process) contacts DNS server, supposedly for
backtranslation of incoming client IP address.
When DNS server not available, time-out after 3 minutes, and
print job completes. During these 3 minutes the UCX$lpd_queue process
has a BG device in the busy state.
If the back translation is needed for security reasons, then I would expect
no completion at all, otherwise it does not make sense.
If it is not for security reasons, I do not understand why the backtranslation
is needed, as the info is in the .cf file.
The customer claims this is a UCX 4.1 behaviour, as he never experienced this
with 3.2, 3.3. (and his DNS server has always been shaky)
Comments please?
Erwin
|
| The discussion in 374.* suggests this is expected behaviour.
Personnally, I think the behaviour is inconsistent.
OR, the lpd request is rejected with a clear error message,
OR the lpd request is accepted and printed right away.
It does not make sense to print after 3 minutes anyway.
Erwin
|