31 Actions

Can lightdm/gnome/compiz use bash instead of sh?Right approach, @Gilles! lightdm starts /usr/sbin/lightdm-session which is a plain #!/bin/sh-shell script which attempts to mimic the shell's login behaviour (including sourcing things like the .profile). This is ugly as hell. Whoever implemented this should be … pyunished (to quote Boss Nass). My current workaround to solve this issue is to patch that script to use /bin/bash instead. Works, but is prone to be overwritten with the next update of the package :-/

Jan14

comment

Can lightdm/gnome/compiz use bash instead of sh?This is a really nice idea to replace the running shell. Unfortunately this loses all the (source-)caller stack; nothing after the exec gets evaluated, whatever script sources us is not going to continue after the source statement. Restarting the script completely is a weak attempt to work around that which in my case does not solve the problem, unfortunately.

Jan14

comment

Can lightdm/gnome/compiz use bash instead of sh?@datUser, yes, that would solve the issue, but applying changes to the system always is a bit problematic (e. g. such a link might get overwritten on the next update of the package which installed the dash), so I would like to avoid that.

Jan14

comment

Can lightdm/gnome/compiz use bash instead of sh?@orion, no, this .profile is not an executable (i. e. not called as such), it is a configuration file which gets sourced by the caller (i. e. it is executed by the caller process) and is supposed to apply changes to the environment. If I call a bash from within it, this creates a new process, and all environment changes this applies get lost when this bash terminates, leaving no changes on the environment of the caller.

Jan14

comment

Can lightdm/gnome/compiz use bash instead of sh?① I intend to do a lot in this script file, so it should be done just once, not each time a new shell is started. Creating shell functions is just one aspect. ② Since I'm talking about the very initial login point, I have no chance to set $SHELL prior to this. I would have expected that $SHELL would be filled with whatever is stated in /etc/passwd, but I guess that compiz just isn't using that variable but instead calls sh hard-wired.

rsyslog.conf only partly honoredYes, the problem remains unsolved. But the workaround is to get the info from the global log file, so it isn't nagging me a lot.

Apr14

comment

Having trouble exporting FUSE via NFSYes, I did. To no avail, unfortunately. But in the meantime we switched off the old hardware with the old system, so this question isn't interesting anymore. I should maybe close it ... ;-)