Difference: APPXLoginManagerForUnixLinux (40 vs. 41)

Revision 412008-06-20 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXConnectionManager"
Added:
>
>
 

APPX Connection Manager For Unix/Linux

This page describes how to install the APPX Connection Manager command and how to use it to install, configure, and manage APPX Connection Services on Unix/Linux systems.
Line: 44 to 45
 In the event that it is necessary to reset the permissions on the appxloginmgr command, the following commands can be run by the root user to set the necessary owner and group permissions for the appxloginmgr command.
Changed:
<
<

cd /usr/local/appx/tools chown root appxloginmgr chgrp appxgrp appxloginmgr chmod 4775 appxloginmgr

>
>

cd /usr/local/appx/tools chown root appxloginmgr chgrp appxgrp appxloginmgr chmod 4775 appxloginmgr

 

You can check the permissions of the appxloginmgr command by running the following command:
Changed:
<
<		ls -l appxloginmgr
>
>		ls -l appxloginmgr
 

The recommended permissions should be as follows:

Line: 517 to 518
 

Testing Results

Deleted:
<
<

004) (Suggestion) Windows' APPXDSVC.exe supports

-status argument by itself to list all APPX services.

For example on Windows:

C:\Appx\appx.42a\tools>appxdsvc -status

Service Name: appxd-8060

Display Name: appxd-8060

Status: running

Service Name: appxd-8074

Display Name: appxd-8074

Status: running

Service Name: appxd-9999

Display Name: appxd-9999

Status: running

C:\Appx\appx.42a\tools>

Now on Linux:

[root@APPX4.30TestBox tools]# ./appxLoginMgr -status

serviceName: -status

servicePath: ./

Looking for config file in -status.ini

Error - can't open configuration file for service -status

No such file or directory

[root@APPX4.30TestBox tools]#

005) (Suggestion) Windows' APPXDSVC supports

-install as sole argument to create initial service on port 8060.

For example on Windows:

C:\Appx\appx.42a\tools>appxdsvc -install

appxd-8060 Configured

appxd-8060 will start automatically each time you boot your system

C:\Appx\appx.42a\tools>

For example on Linux:

[root@APPX4.30TestBox tools]# ./appxLoginMgr -install

serviceName: -install

servicePath: ./

Looking for config file in -install.ini

Error - can't open configuration file for service -install

No such file or directory

[root@APPX4.30TestBox tools]#

006) (Suggestion) Rename .ini, .env and service

names to match new names of appxLoginMgr and appxAuditLogger.

Current value is appxd-NNNN where NNNN is the port number.

Should be perhaps appxLoginListener-NNNN for appxLoginMgr files/services

Should be perhaps appxAuditLoggerListener-NNNN for appxAuditLogger files/services

007) (Suggestion) appxLoginMgr service creation

does not initialize required environment variable APPX_KEYMAP, results in hung client on TCP logins.

Probably should set APPX_KEYMAP = WINDOWS in appxLoginListener-NNNN.env file.

008) (Error) Service definition files can get

created in current working directory, which may not be where one wants them to be created.

An example on Linux follows:

[root@APPX4.30TestBox appx]# pwd

/appx

[root@APPX4.30TestBox appx]# ls

[root@APPX4.30TestBox appx]# /usr/local/appx/tools/appxLoginMgr -install -port=8060 -engine=/usr/local/appx/appx

Warning - the engine that you named has the setuid bit enabled,

you may not want that bit set for the authentication

method that you have chosen (OS-User)

To turn off the setuid bit, chmod u-s /usr/local/appx/appx

Configuration written to: appxd-8060.ini

Environment written to: appxd-8060.env

Service script written to: /etc/init.d/appxd-8060

Configuration complete

Registering service

Starting appxd-8060: serviceName: appxd-8060

servicePath: /appx/

Looking for config file in appxd-8060.ini

Warning - the engine that you named has the setuid bit enabled,

you may not want that bit set for the authentication

method that you have chosen (OS-User)

To turn off the setuid bit, chmod u-s /usr/local/appx/appx

Writing process ID to /var/run/appxd-8060.pid

running as process 7803 servicing port 8060

Warning - the engine that you named has the setuid bit enabled,

you may not want that bit set for the authentication

method that you have chosen (OS-User)

To turn off the setuid bit, chmod u-s /usr/local/appx/appx

up and running (process 7803 servicing port 8060)

Installation Complete

[root@APPX4.30TestBox appx]# ls

appxd-8060.env appxd-8060.ini

[root@APPX4.30TestBox appx]# ls /usr/local/appx/tools/appxd-8060*

ls: /usr/local/appx/tools/appxd-8060*: No such file or directory

[root@APPX4.30TestBox appx]#

009) (Suggestion) Possible inconsistent

requirement of the -name argument.

It seems we are inconsistent in our requirements for the use of the -name argument. Examples follow where (+) works and (-) does not currently work.

(-) ./appxLoginMgr -modify appxd-8060 -TCPNodelay=false

(+) ./appxLoginMgr -modify -name=appxd-8060 -TCPNodelay=false

(-)./appxLoginMgr -status

(+)./appxLoginMgr -status -name=appxd-8060

(+) ./appxLoginMgr -stop appxd-8060

(-) ./appxLoginMgr -stop -name=appxd-8060

(+) ./appxLoginMgr -start appxd-8060

(-) ./appxLoginMgr -start -name=appxd-8060

(-) ./appxLoginMgr -remove appxd-8060

(+) ./appxLoginMgr -remove -name=appxd-8060

(-) ./appxLoginMgr -status

(+) ./appxLoginMgr -status appxd-8060

(+) ./appxLoginMgr -status -name=8060

 

010) (Error) The argument -replace erroneously

does not require the “-name” argument
Line: 913 to 680
 to work. The /etc/inid.d/appxd-8060 startup script references by name and path the .ini, .env, and appxLoginMgr/appxAuditLogger files.
Changed:
<
<

Suggested Behavior:

>
>

Suggested Behavior changes:

 
  1. To match the Windows platform, he following should be valid syntax: "appxLoginMgr -install". It should default to port 8060, or the Windows platform should not default to port 8060.
  2. To clarify the purpose of the file, consider renaming uappxd/appxdsvc to appxLoginMgr on all platforms.
  3. To clarify the purpose of the file, consider renaming uappxd/appxdsvc to appxAuditLogger
Changed:
<
<
  1. In an effort to make appxdsvc and uappxd (appxLoginMgr) as similar as possible, consider allowing -status as a single argument.
Windows' APPXDSVC.exe supports -status argument by itself to list all APPX services.

For example on Windows:

C:\Appx\appx.42a\tools>appxdsvc -status

>
>
  1. In an effort to make appxdsvc and uappxd (appxLoginMgr) as similar as possible, consider allowing -status as a single argument that would list all appxLoginMgr daemons.  (Perhaps this isn't practical on Unix platforms)
  2. APPX_KEYMAP environment variable should be initialized upon default install options.  Currently "appxLoginMgr -install -SockPort=8060" does not place APPX_KEYMAP into appxLoginMgr-8060.env.
  3. appxLoginMgr should create .ini and .env files in the tools subdirectory, and not in the current working directory.
  4. The requirements for use of -name argument seem inconsistant.  Below are examples where + works, and - does not.

    1. (-) ./appxLoginMgr -modify appxd-8060 -TCPNodelay=false

    2. (+) ./appxLoginMgr -modify -name=appxd-8060 -TCPNodelay=false
    3. (-)./appxLoginMgr -status
    4. (+)./appxLoginMgr -status -name=appxd-8060
    5. (+) ./appxLoginMgr -stop appxd-8060
    6. (-) ./appxLoginMgr -stop -name=appxd-8060
    7. (+) ./appxLoginMgr -start appxd-8060
    8. (-) ./appxLoginMgr -start -name=appxd-8060
    9. (-) ./appxLoginMgr -remove appxd-8060
    10. (+) ./appxLoginMgr -remove -name=appxd-8060
    11. (-) ./appxLoginMgr -status
    12. (+) ./appxLoginMgr -status appxd-8060
    13. (+) ./appxLoginMgr -status -name=8060
Bugs:
 
Changed:
<
<		Service Name: appxd-8060

Display Name: appxd-8060

Status: running

Service Name: appxd-8074

Display Name: appxd-8074

Status: running

Service Name: appxd-9999

Display Name: appxd-9999

Status: running

C:\Appx\appx.42a\tools>

Now on Linux:

[root@APPX4.30TestBox tools]# ./appxLoginMgr -status

serviceName: -status

servicePath: ./

Looking for config file in -status.ini

Error - can't open configuration file for service -status

No such file or directory

[root@APPX4.30TestBox tools]#

Bugs:

  1. Fixed - Bug 2090 uappxd doesn't remove a running service.
>
>
  1. Fixed - Bug 2090 uappxd doesn't remove a running service.
 

Comments:

Read what other users have said about this page or add your own comments.
View topic | History: r68 < r67 < r66 < r65 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback