On Tue,12.May.09, 22:19:48, Joachim Breitner wrote: > > Some more investigation reveals that the SHELL environment is not > > properly set on first start, but if nodm is restarted > > (/etc/init.d/nodm restart) then everything is fine. > > this is not surprising: When you restart nodm, you are obviously running > in some shell that has set the SHELL variable. (You could verify that) I was doing the restart from a ssh connection (and 'su -'). Now I rebooted, switched to VT6, logged in as root and ran '/etc/init.d/nodm restart'. Everything ok. I disabled nodm with sysv-rc-conf, rebooted and then started it by hand. Again, everything ok.
Now it seems to me that the issue is due to insserv (didn't mention it before, because I didn't think it was relevant) so I'm attaching a bootchart, maybe you can spot something wrong. I already tried to add $local_fs to Required-Start (same as gdm), but it didn't help. > This leads to the question whether nodm should clean it’s environment, > and it probably should – again, help would be appreciated in seeing what > xdm or gdm do: What of their environment do they retain, what do they > delete and what do they actively set. I'm running gdm with autologin and the environment is setup correctly on the first start. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein)
bootchart.tgz
Description: GNU Unix tar archive
signature.asc
Description: Digital signature
