|
smxi and closing down X using nodm
hi
I have moved off login managers like gdm3. kdm, xdm slim etc and moved to nodm I have it autologin as I am single user on pc I used to shutdown X with either root commands :: Code ::
smxi init3 but nodm just respawns the desktop....for me E17 the trick is just shut down nodm with :: Code ::
/etc/init.d/nodm stop and Bob's your uncle.....now I can run smxi good lcu Back to top |
|
nodm is a new one on me, I'll add it to the x shutdown dm list.
Back to top |
|
oh I forgot to mention some traits of nodm that may interest your readers
apparently it is mainly used by kiosks anyhow....if you "logout" it does not log out but respawn your preferred desktop if you want to startx....startup nodm with :: Code ::
/etc/init.d/nodm start 2) As I am probably the only one using it at this stage....no need to add it as it might require an if -then to search for nodm script for smxi to shutdown X. These are my online notes to myself so lets leave smxi alone? Back to top |
|
smxi loops through a range of dms, so it's not an issue adding one. I'll update it and let me know if it works.
With login via nodm, please post the output of the following: ls /var/run | grep nodm so I can find what to look for, it's either going to be a nodm.pid or nodm.lock unless it's a new one. Back to top |
|
well as long as it does not distract you from your other work
:: Code ::
ls /var/run | grep nodm nodm.pid Back to top |
|
stuff like this is trivial to update, so might as well, it's now updated.
Back to top |
|
You may be right I think the fault lies with the person typing at the moment.
or maybe because ....strictly speaking nodm means no display manager....so tricks smxi running the shutdown desktop command respawns desktop back to E17 with a message that appears of something like...."can't find /etc/init.d/slim" because I have remove and purged slim hmm when I moved from slim to nodm.....I thought I did it correctly but smxi updated and fails as it thinks slim is my login manager. Here is log snippet :: Quote ::
========================================================= START smxi LOGGING: ========================================================= Script started: 2012-01-30-12:00:51 Installed Kernel: 3.2.0-1.dmz.6-liquorix-686 smxi script version: 8.14.7 smxi start args: ========================================================= Function: check_display_and_x - Primary: Start Function: get_display_manager_runlevels - Utility: Start Function: get_default_display_manager - Utility: Start displayManager: slim Function: get_default_display_manager - Utility: End dmRunlevels: Function: get_display_manager_runlevels - Utility: End Function: do_display_manager_pid_test - Utility: Start Function: x_is_running - Utility: Start returnVal: 0 Function: x_is_running - Utility: End found: true Function: do_display_manager_pid_test - Utility: End Function: check_display_and_x - Primary: End opt selected: shutdown-your-desktop Function: start_stop_default_dm - Utility: Start Args: full stop Function: get_default_display_manager - Utility: Start displayManager: slim Function: get_default_display_manager - Utility: End Function: x_is_running - Utility: Start returnVal: 0 Function: x_is_running - Utility: End 2) here is /etc/smxi.conf :: Quote ::
apt-type=apt-get busybox-fix-1 debian-mirrors-1 distro-kernel=liquorix du-connection-drop-1 du-upgrade=dist-upgrade keyrings-update-4 libc6-fix-4 nvidia-sse-test-1 reconfigure-locales RememberResponses script-last-du-complete=2012-01-28-10:11 script-last-used=2012-01-28-10:10 udev-kernel26-fix-1 update-nonfree-1 3) /usr/loca/bin/smxi lines of interest may be 2016 2052 2191 2207 4) if of interest here is my init.d output :: Code ::
ls /etc/init.d acpid console-setup halt kbd mountall-bootclean.sh networking reboot single umountfs alsa-utils cpufrequtils hostname.sh kexec mountall.sh nodm resolvconf skeleton umountnfs.sh anacron cron hwclockfirst.sh kexec-load mountdevsubfs.sh pppd-dns rmnologin ssh umountroot bootlogd cups hwclock.sh keyboard-setup mountkernfs.sh procps rsync stop-bootlogd urandom bootlogs dbus ifplugd keymap.sh mountnfs-bootclean.sh rc rsyslog stop-bootlogd-single virtualbox bootmisc.sh dns-clean ifupdown killprocs mountnfs.sh rc.local saned sudo x11-common checkfs.sh fuse ifupdown-clean loadcpufreq mountoverflowtmp rcS screen-cleanup udev checkroot.sh gpm irqbalance module-init-tools mtab.sh README sendsigs udev-mtab Back to top |
|
this file has the default display manager, and it's what sgfxi/smxi check. If that is set, smxi/sgfxi will use that, if it is not, it will loop through them all and check if they are running.
/etc/X11/default-display-manager probably still has slim. I've found slim to be too buggy to use, and I assume it didn't clean up after itself when you removed it. Or is that a packaging bug? Also try: grep -Rsn slim /etc/* to see where else it is mentioned. Back to top |
|
Thats great
changing that etc/X11 file did the trick there are dishonourable mentions from the grep output but smxi now logs out of X. Strangely :: Code :: dpkg-reconfigure nodmon my system never attempts to write to that display manager file. But I am still assuming its because its not a display manager? any how that you muchly regards Back to top |
|
All times are GMT - 8 Hours |