Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - David McKenna

Pages: [1] 2 3 ... 50
1
Networking / Re: apache2.4 configuration
« on: Today at 09:20:44 pm »
 Greg,

  That's what I have been doing:

/* Rexx script to shut down Apache */

pid = linein("logs\httpd.pid")
kill.exe pid

 in a CMD file originally installed by AMP for OS/2 way back when. Never tried the apachectl way until you posted. There is an Apache for OS/2 google group you could post on to see if anyone there has experience with apachectl...

Regards,

2
Networking / Re: apache2.4 configuration
« on: March 25, 2024, 02:33:37 pm »
Greg,

  Oops! forgot the 'sh' I now get this:

[C:\programs\apache24\bin]sh apachectl -k stop
apachectl: 101: apachectl: /apache24/bin/httpd: not found

 Definitely something not right...

EDIT: after editing apachectl to have the correct HTTPD directory listed, if I try 'sh apachectl -f /Programs/apache24/conf/httpd.conf -k stop' I get an 'killed by SIGSEGV'  exceptq trap file...

Regards,

3
Networking / Re: apache2.4 configuration
« on: March 25, 2024, 12:10:19 am »
Greg,

  Hmm... I get this:

[C:\programs\apache24\bin]apachectl -k stop
SYS1041: The name apachectl is not recognized as an
internal or external command, operable program or batch file.

I'm using Paul's version 2.4.57 of httpd. Maybe report this at his Mantis site: https://mantis.smedley.id.au/my_view_page.php

Regards,

4
Networking / Re: Updated Samba Client
« on: February 25, 2024, 03:42:20 pm »
Thanks Paul!

  This 4.19.5 server seems to perform about the same as the 4.19.4 version, except WINBINDD will not start - log ends with this message:

[2024/02/25 09:07:58.200000,  5] ../../librpc/rpc/dcesrv_core.c:430(dcesrv_interface_register_b)
  dcesrv_interface_register_b: Interface 'winbind' registered on endpoint 'ncalrpc:' (single process required)
[2024/02/25 09:07:58.200000,  1] ../../source3/winbindd/winbindd.c:1038(winbindd_setup_listeners)
  lp_winbindd_socket_directory() = \socket\winbindd, WINBINDD_SOCKET_NAME = pipe
[2024/02/25 09:07:58.200000,  0] ../../lib/util/util.c:225(directory_create_or_exist)
  directory_create_or_exist: mkdir failed on directory \socket\winbindd: No such file or directory
[2024/02/25 09:07:58.200000,  0] ../../lib/util/become_daemon.c:123(exit_daemon)
  exit_daemon: daemon failed to start: Winbindd failed to setup listeners, error code 32

 Didn't we see something like this before?

Regards,

EDIT: added net rpc user log for comparison...

5
Networking / Re: Updated Samba Client
« on: February 22, 2024, 11:17:00 pm »
Hey Paul,

 Curious how your theory panned out...

Regards,

6
Applications / Re: Test build of dooble with qt5
« on: February 22, 2024, 11:12:57 pm »
Dave,

  Thanks for the updates... seem to be working well here. No more db file in the root... Haven't seen that in the QT6 versions, but the latest hasn't been ported yet.

Regards,

7
Comments, Suggestions & Questions / Re: Hobbes (Files) Reoganization
« on: February 16, 2024, 11:33:35 pm »
 Thanks Martin and Nathan for keeping Hobbes alive! Very important resource for OS/2 users on the web.

Thanks!

EDIT: I notice on the main page mirror 'OS/2 Site Australia' is shown to be in the USA? I doubt it...

 Also was not able to register an account - got a generic 'something went wrong' error...

8
Applications / Re: Test build of dooble with qt5
« on: February 13, 2024, 01:48:47 am »
 Dave,

 Well, it kinda works here (I think) only if the jar file is on my unixroot drive. But all it does is display the contents - if I click on any file displayed nothing happens. What exactly is it supposed to do?

 One weird thing: I get a new 'dooble_settings.db' file in the root of my boot drive with this version. Never had that before...

Regards,

9
Applications / Re: Test build of dooble with qt5
« on: February 12, 2024, 10:39:35 pm »
 Thanks - got it. So far it works fine. Also got the zip file and there is a 'Data' folder in there with a couple of jar files that are not in the rpm. What are they?

Regards,

10
Applications / Re: Test build of dooble with qt5
« on: February 12, 2024, 10:26:15 pm »
 Thanks Dave! Tried to get the rpm, but it wants a password to login. Can you give the password?

Regards,

11
Networking / Re: Updated Samba Client
« on: February 08, 2024, 11:16:46 pm »
 Hey Paul,

 Spent the last couple of evenings pondering the forgotten lore of Netlabs SAMBA apps code to try to figure out the SMBTREE command that causes the trap in server 4.19 and it seems to be something like this:

SMBTREE -S -N -d 2 2>smberror.txt 1>smbtree.txt

 I'll attach the results. They show a trap, and I tried with both 'null passwords = Yes' and 'No' in smb.conf, but no difference.

 So also tried SMBTREE -S -U DaveM%password -d 2 2>smberror2.txt 1>smbtree2.txt

 and don't get a trap, but it still doesn't seem to work quite right - I'll attach them too. The SMBMon app probably needs to be updated to work properly with server 4.19 in any case...

 Comparing the logs for 'net rpc user' from the 4.15 and 4.19 server, it seems the 4.19 server doesn't even use the 'rpc' part - it is completely missing from the log...

Regards,




12
Networking / Re: Updated Samba Client
« on: February 05, 2024, 10:24:22 pm »
 Thanks Dave! I forgot about that...

 Attached are the full results for the 4.15 and 4.19 servers...

Regards,

13
Networking / Re: Updated Samba Client
« on: February 05, 2024, 12:19:00 pm »
Paul,

 I see the same as you with server 4.19 with 'net rpc user -d 10' at the end:

gensec_update_send: spnego[20049570]: subreq: 2004b1a0
gensec_update_done: spnego[20049570]: NT_STATUS_OK tevent_req[2004b1a0/../../aut
h/gensec/spnego.c:1631]: state[2] error[0 (0x0)]  state[struct gensec_spnego_upd
ate_state (2004b2a0)] timer[0] finish[../../auth/gensec/spnego.c:2116]
 session setup ok
signed SMB2 message (sign_algo_id=2)
 tconx ok
     NetQueryDisplayInformation: struct NetQueryDisplayInformation
        out: struct NetQueryDisplayInformation
            entries_read             : *
                entries_read             : 0x00000000 (0)
            result                   : UNKNOWN_ENUM_VALUE (2152)
return code = 2152
Freeing parametrics:

 and server 4.15 shows at the end:

[0000] 00 00 00 00 00 00 00 00   00 00 00 00 00 00 00 00   ........ ........
[0010] 00 00 00 00 00 00 00 00                             ........
Got pdu len 48, data_len 24
rpc_api_pipe: got frag len of 48 at offset 0: NT_STATUS_OK
rpc_api_pipe: host localhost returned 24 bytes.
     samr_Close: struct samr_Close
        out: struct samr_Close
            handle                   : *
                handle: struct policy_handle
                    handle_type              : 0x00000000 (0)
                    uuid                     : 00000000-0000-0000-0000-000000000
000
            result                   : NT_STATUS_OK
Freeing parametrics:

 Couldn't figure out how to capture the whole thing - is there a way?

 I'll look at the Rexx code of the SAMBA Status Monitor (on the Netlabs Trac site) and see if I can figure out the actual SMBTREE command used there after work...

Regards,


14
Networking / Re: Updated Samba Client
« on: February 04, 2024, 05:45:43 pm »
Hey Paul,

 I have been using the Netlabs 3.6 SAMBA WPI to install SAMBA on my machine, then use the 'SAMBA Simple Configuration Center' app to update it with your binaries. This has worked well enough, except now the 'SAMBA Users and Groups' app gives an error when run after updating to your current 4.19.4 binaries. From what I have been able to determine, 'SAMBA Users and Groups' uses 'net rpc xxxx' commands to manipulate the users and groups in SAMBA databases. Did some testing to see if I could figure out why it doesn't work...

 After installing the 3.6 wpi, I am able to issue say -  'net rpc user' - on a command line and after entering a password it lists all users set up for SAMBA. Other 'net rpc xxx' commands also work.

 After upgrading to 4.19.4, when I enter 'net rpc user', after entering a password I get nothing (no error, it just returns to the prompt). So that explains the error I get when trying to run 'SAMBA Users and Groups'. Is this a bug?

EDIT: I went thru and tried each of your SAMBA builds starting with 4.11. SAMBA Users and Groups worked with 4.11, 4.13 and 4.15, but not 4.18 and 4.19.

 The 'SAMBA Status Monitor' 'Nethood' tab also gives an error (other tabs work fine), and I get an exceptq log in SMBTREE - I'll attach.

EDIT: 4.11 was the last build 'Nethood' worked with.

Regards,

15
Networking / Re: Updated Samba Client
« on: February 03, 2024, 10:04:43 pm »
Paul,

  Client 20240127 seems to work fine...

Regards,

Pages: [1] 2 3 ... 50