Re: CTWM and XDM

--pgp-sign-Multipart_Tue_Apr_15_10:13:59_2025-1
Content-Type: text/plain; charset=US-ASCII

At Tue, 15 Apr 2025 11:20:02 +0100, BC HABS <[email protected]> wrote:
Subject: CTWM and XDM
>
> XDM is started (no session manager/management) on boot .  Once logged
> in, ctwm is loaded as the last command in xsession.
>
> when using f.restart, ctwm is closed down and not restarted with XDM
> login taking over ... unlike that which happened under twm, where
> f.restart simply restarted (e.g. for reflecting config file updates) .

Very odd behaviour!

I wonder if you might be able to find a clue either in the logs.  The
code for doing a restart has printfs on both sides of the execvp(), so
you should always see the message "ctwm:  restarting: ctwm ...", and if
you see the second message "ctwm:  unable to restart: ctwm ..." then the
problem is that Ctwm is unable to exec itself.

	// Re-run ourself
	fprintf(stderr, "%s:  restarting:  %s\n", ProgramName, *Argv);
	execvp(*Argv, Argv);

	// Uh oh, we shouldn't get here...
	fprintf(stderr, "%s:  unable to restart:  %s\n", ProgramName, *Argv);

Unfortunately nothing about the cause of the error is printed, but just
knowing that's where the failure is should allow for further debugging.

Most X11 systems using XDM will have a system Xsesssion script that will
create an output file in $HOME, usually ~/.xsession-errors.  It should
contain all the stdout and stderr from both itself and your ~/.xsession
script.

--
					Greg A. Woods <[email protected]>

Kelowna, BC     +1 250 762-7675           RoboHack <[email protected]>
Planix, Inc. <[email protected]>     Avoncote Farms <[email protected]>

--pgp-sign-Multipart_Tue_Apr_15_10:13:59_2025-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
Content-Description: OpenPGP Digital Signature

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQRuK6dmwVAucmRxuh9mfXG3eL/0fwUCZ/6T3AAKCRBmfXG3eL/0
f+SgAJ9NV26Xr1jiZiI7NR4bm03d1A3kGwCffTG0V+s+Ci9igTJeQY4KLYSJues=
=I8rC
-----END PGP SIGNATURE-----

--pgp-sign-Multipart_Tue_Apr_15_10:13:59_2025-1--