Tim Johnson wrote: > * Gregor Best <[email protected]> [100720 23:55]: >> keep in mind though that this starts nm-applet whenever awesome is >> restarted. That also includes screen geometry changes (i.e. xrandr >> events), such as connecting another screen. > Is there a command to first shut down nm-applet (and that command > might need to be error-trapped)? Then restart, thus avoiding > and redundancies. > What do you folks do? > Look at the man pages for pkill and pgrep. To start command foo unless it's already running, I use:
pgrep foo > /dev/null 2>&1 || foo &
>> The appropriate place to
>> start programs would be your ~/.Xsession or ~/.xinitrc, depending on
>> which is used by your login manager. A working bare bones session file
>> would look like this:
>>
>> #!/bin/bash
>>
>> nm-applet &
>> exec awesome
> No success using either startup file.
> I don't think the login manager is reading either of the files
> above. Darn ubuntu.
>
Well I don't like Ubuntu, but they are not to blame for this one.
Recent display managers (like gdm and kdm) don't run the .Xsession
and .xinitrc files. Instead they rely on a set of .desktop files to
describe the available desktop environments and let the user choose
from a menu (although there might be one entry to execute .Xsession
instead of launching a DE). Personally, I put the commands I want
started automatically in ~/.xprofile (which is a bit of a hack since
.xprofile is supposed to be used for setting environment variables,
but it works).
Jerome
--
mailto:[email protected]
http://jeberger.free.fr
Jabber: [email protected]
signature.asc
Description: OpenPGP digital signature
