OS/2, eCS & ArcaOS - Technical > Networking

Updated Samba Client

<< < (42/46) > >>

David McKenna:
Hey Paul,

  Something seriously wrong with this one - soon as I start the server the computer freezes solid. Have to hit the reset switch (or turn it off). No POPUPLOG, no exceptq trap reports or anything left behind as a clue. Had to boot to a AOS DVD and delete from there, then re-install your last drop of 4.19.7 (which works well)...

Regards,

Paul Smedley:
Interesting, smbd starts/runs fine here and can accept connections.....

Steven Levine:
David,

Can I assume that CAD failed to pop up CADH?

If you can get CADH to pop up, you can usually capture a process dump, even if you cannot kill the app that is hung.

If CADH will not pop up, you could try to capture a system dump.  This would likely tell us where smbd is going astray.

Steven

David McKenna:
 Steven,

  Couldn't get to CADH - no mouse or keyboard input was working. I have some more time today, so I'll try again and see if I can get it to work. If not, I'll try to get a dump.

Regards,

Steven Levine:
David,

Most of the time, Ctrl-Alt-F10-F10 will bring up the system dump prompts, even if the keyboard is not responding to normal keystrokes.  Whether or not you will be able to capture a system dump, depends on your boot environment, much more than it used to.

Depending on what starting smbd breaks, you still might be able to capture a process dump.

 - open a command line session where you will start smbd
 - open a 4os2 session where you will manage the process dump facility
 - configure the process dump facility with something like
      pdumpctl n f v smbd
     delay 30 & pdumpctl f smbd
 - switch to the smbd command line session and start smbd

If the system is sufficiently alive after smbd starts, pdumpctl will force a process dump after 30 seconds

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version