| Well - apparently he thought that like UNIX, UCX would just have editable
files to define things like services... he didn't even know the UCX command
existed... now that he's using it, he sent me the following. I know he's
missing some qualifiers (like/username, /process_name, and /file), but it
looks like his main problem is that fact that he wants one service ("sq") on
port 40000 to use two protocols, both tcp and udp... apparently UCX doesn't
allow that... how can he get around this ??
Thanks
Arlan
--------------------------------------------------------------------------------
OK, I shoulda known there wouldn't be an editable text file akin to
/etc/services. I found this utility called UCX which allows me to
define services via the "SET SERVICE" command.
But I've got a problem. A la the PORTMAPPER, I have a service which
uses both TCP port 40000 and UDP port 40000. However, I am having
no success at defining my own service to use both protocols. The
command
UCX> set service sq/port=40000/proto=(tcp,udp)
gives the error
%CLI-W-CONFLICT, illegal combination of command elements - check
documentation
\TCP\
|
| Haven't checked the exact command syntax, but i can be done. For instance
the bind service looks like:
UCX> sho service bind/fu
Service: BIND
State: Enabled
Port: 53 Protocol: TCP,UDP Address: 0.0.0.0
Inactivity: 0 User_name: UCX$BIND Process: UCX$BIND
Limit: 1 Active: 1 Peak: 1
[etc]
Oswald
|
| re: .3
>Haven't checked the exact command syntax, but i can be done. For instance
>the bind service looks like:
>
Just found note 3707 -- looks like it can NOT be done, that bind,
portmapper and other services are "special cases" using an undocumented
qualifier (/flags=ucx) which does not work for generic services.
Arlan
|