multinet_''username'_ftp_directory

[Christoph Gartmann]

Hello,

I can't get the above logical "MULTINET_USERNAME_FTP_DIRECTORY" to work.
The current setup: the user's login directory and LOGIN.COM is on DISK:[DIR].
The FTP directory is on DISK2:[DIR2]. So the FTP user's login.com contains
the following:

$ IF modus .EQS. "NETWORK" ! we assume it is FTP
$ THEN
$ DEFINE multinet_TEST_ftp_directory "diskb:[www.groups.transfer]"
...

But the user always ends up in DISK:[DIR] when connecting via FTP. Why?
Multinet V5.1 under OpenVMS 7.3-2.

Regards,
Christoph Gartmann

[Ken Connelly]

I think this has to be a system-level logical name, probably normally
defined in SYLOGICALS.COM. Try:

$ def/sys multinet_test_ftp_directory diskb:[www.groups.transfer]

and see how that does for you.

-ken

Post by Christoph Gartmann
Hello,
I can't get the above logical "MULTINET_USERNAME_FTP_DIRECTORY" to work.
The current setup: the user's login directory and LOGIN.COM is on DISK:[DIR].
The FTP directory is on DISK2:[DIR2]. So the FTP user's login.com contains
$ IF modus .EQS. "NETWORK" ! we assume it is FTP
$ THEN
$ DEFINE multinet_TEST_ftp_directory "diskb:[www.groups.transfer]"
...
But the user always ends up in DISK:[DIR] when connecting via FTP. Why?
Multinet V5.1 under OpenVMS 7.3-2.
Regards,
Christoph Gartmann

[Christoph Gartmann]

Post by Ken Connelly
I think this has to be a system-level logical name, probably normally
$ def/sys multinet_test_ftp_directory diskb:[www.groups.transfer]
and see how that does for you.

Oh, I see, this does the trick. It should be mentioned in the docs, though.

Thank you very much
Christoph Gartmann

[Michael Corbett]

Post by Ken Connelly
I think this has to be a system-level logical name, probably normally
$ def/sys multinet_test_ftp_directory diskb:[www.groups.transfer]

It does have to be in the system table. FTP_SERVER.COM does the following
check -

$ Directory = F$TrnLNM("MULTINET_''Username'_FTP_DIRECTORY","LNM$SYSTEM")
$ If Directory .Nes. "" Then -
FtpOptions = FtpOptions + "/DIRECTORY=(''Directory')"
$ !

It does this so an unprivileged user can not define a group, job, or
process logical and circumvent the logical. You could change this so
if the logical is not in LNM$SYSTEM it then checks all the other
tables. Something like -

$ Directory = F$TrnLNM("MULTINET_''Username'_FTP_DIRECTORY","LNM$SYSTEM")
$ If Directory .eqs. "" Then -
Directory = F$TrnLNM("MULTINET_''Username'_FTP_DIRECTORY")
$ If Directory .Nes. "" Then -
FtpOptions = FtpOptions + "/DIRECTORY=(''Directory')"
$!

regards
Mike

[Christoph Gartmann]

Post by Michael Corbett

Post by Ken Connelly
I think this has to be a system-level logical name, probably normally
$ def/sys multinet_test_ftp_directory diskb:[www.groups.transfer]

It does have to be in the system table. FTP_SERVER.COM does the following
check -
$ Directory = F$TrnLNM("MULTINET_''Username'_FTP_DIRECTORY","LNM$SYSTEM")
$ If Directory .Nes. "" Then -
FtpOptions = FtpOptions + "/DIRECTORY=(''Directory')"
$ !
It does this so an unprivileged user can not define a group, job, or
process logical and circumvent the logical.

No problem in our case, I can live with the /SYSTEM definition. The only thing
was the documentation that describes all these MULTINET_FTP* logicals which
work in user mode besides this specific one.

Regards,
Christoph Gartmann