Re: I Have Two Instances Of 'autostart.sh Running...

On Tue, Oct 21, 2014 at 2:35 AM, E R <[email protected]> wrote:

> So I've gone through everything again and all I can think of.
>
> Again, for some reason using the sleep cmd to run an app causes this
> and this shouldn't happen.
>

doesn't (sleep 1 && foo) cause the shell to fork?


> Also something I forgot to mention, that application in question, I
> don't see them running in htop when using sleep, instance I just see
> it showing autostart.sh running....
>
> So here's how I made it look now;
>
> # This shell script is run before Openbox launches.
> # Environment variables set here are passed to the Openbox session.
>
> # D-bus
> if which dbus-launch >/dev/null && test -z "$DBUS_SESSION_BUS_ADDRESS";
> then
>        eval `dbus-launch --sh-syntax --exit-with-session`
> fi
>
> # Run XDG autostart things.  By default don't run anything desktop-specific
> # See xdg-autostart --help more info
> #DESKTOP_ENV="OPENBOX"
> #if which /usr/libexec/openbox-xdg-autostart >/dev/null; then
> #  /usr/libexec/openbox-xdg-autostart $DESKTOP_ENV
> #fi
>
> compton --config ~/.config/compton -b --logpath /tmp/compton.log &
> tint2 &
> redshift-gtk >/dev/null 2>&1 &
> /usr/lib64/xfce4/notifyd/xfce4-notifyd &
> xbindkeys &
> eval `cat $HOME/.fehbg` &
>
> # For use with BFS
> #sudo schedtool -n -20 -I `pidof X`
>
> To be honest I don't need anything to sleep and now I see tint2 and
> redshift appearing in htop...
>
> Hopefully Dana, OH DANA! :) What's going on here?
>
> I still say --> BUG hehe... :)
>
>
> On Mon, Oct 20, 2014 at 8:17 PM, E R <[email protected]> wrote:
> > Yes I added the brackets back.
> >
> >
> > For the problem.culprit I'm saying it appears to be openbox because if
> > I make the autostart command as sleep like this; ( sleep 1 && tint2 )
> > & then I see an instance of autostart.sh running in htop, but if just
> > made tint start like this; tint2 & nothing appears. You understand
> > now?
> >
> > I know that sh starts the script, that is not what I was talking
> > about. Tint2 is an application, autostart.sh is a script, so I don't
> > really get why it should appear in htop as a running process is what I
> > meant...
> >
> > I've always used it as autostart.sh, but I'll rename it and try...
> >
> > I don't use a display manager, just startx and I'm running Slack...
> >
> > Also my understanding is only something you want to sleep you put
> > brackets around it, not just anything that ends in ampersand &...
> >
> > So as I mentioned the culprit seems to be running a command as; (sleep
> > 1 && appname) &
> >
> > On Mon, Oct 20, 2014 at 10:03 AM, TT <[email protected]> wrote:
> >> E R wrote:
> >>>
> >>> tint2 & redshift are both showing these instances, but if I
> >>> don't make them sleep then I don't even see one instance of autostart
> >>> running...
> >>
> >> on second thought, your bash syntax is probably off somewhere here:
> >> try putting brackets around everything that has a "&" in the end - and
> maybe
> >> something else, don't know, just guessing here.
> >> try commenting out lines until you find the CULPRIT.
> >>>
> >>> compton --config ~/.config/compton -b --logpath /tmp/compton.log &
> >>> sleep 1s && tint2 &
> >>> sleep 2s && redshift-gtk >/dev/null 2>&1 &
> >>> /usr/lib64/xfce4/notifyd/xfce4-notifyd &
> >>> /usr/bin/xbindkeys &
> >>> eval `cat $HOME/.fehbg`
> >>>
> >>>
> >>
> >> _______________________________________________
> >> openbox mailing list
> >> [email protected]
> >> http://icculus.org/mailman/listinfo/openbox
> _______________________________________________
> openbox mailing list
> [email protected]
> http://icculus.org/mailman/listinfo/openbox
>

_______________________________________________
openbox mailing list
[email protected]
http://icculus.org/mailman/listinfo/openbox