|
It looks from the replies here and elsewhere that there is no fix for this problem, only many different workarounds !
That's because the job description only comes into play when a job is created. Job's don't switch job descriptions in the middle of a job.
In the case of FTP, this is what it does: a) A central job waits for connections.b) When a connection is received, a new job is started to handle that connection. This job is started according to it's job description.
c) The new job then starts talking to the FTP client that has connected. Not until this communication is active does the FTP client ask the user to key in his userid and password.
Since the userid hasn't been established yet at the time that the FTP job is started, there's no way that it could pick up user-specific settings from the user profile.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
