On Sat, Sep 14, 2002 at 07:51:04PM +0200, Christoph Claus wrote:
> exec $XWINDOWMANAGER
I never though about setting into variables like that. I use a
similar function for switching in and out of .xinitrc's at specific
run-levels:
start()
{
echo -n $"Starting $prog:"
rm -f /home/time/.xinitrc
echo '#!/bin/bash' > /home/time/.xinitrc
ln -sf /etc/X11/XF86Config-4.v102 /etc/X11/XF86Config-4
echo 'exec ut' >> /home/time/.xinitrc && success || failure
RETVAL=$?
[ "$RETVAL" = 0 ]
echo
}
stop()
{
echo -n $"Stopping $prog:"
rm -f /home/time/.xinitrc
echo '#!/bin/bash' > /home/time/.xinitrc
echo 'exec /usr/bin/xscreensaver -no-splash &' >>
/home/time/.xinitrc
ln -sf /etc/X11/XF86Config-4.v101 /etc/X11/XF86Config-4
echo 'exec /usr/bin/enlightenment' >> /home/time/.xinitrc && success
|| failure
RETVAL=$?
[ "$RETVAL" = 0 ]
echo
}
Which spawns the question:
How would one set a specific user's environment variables from an init
script where
that variable would be accessible immediately and without having to
logout/login/reset the shell session?
--
Regards,
Time
13
\
9 . 3 clockbot.net
/
6
Attachment:
pgpeUw5rX4L3A.pgp
Description: PGP signature