On Tue, May 28, 2019 at 04:52:52PM -0400, Gene Heskett wrote: > On Tuesday 28 May 2019 01:32:31 pm Reco wrote: > > > On Tue, May 28, 2019 at 01:23:45PM -0400, Gene Heskett wrote: > > > > End users can remove that '-e' flag if they believe it's > > > > problematic. rc.local is a simple shell script, open to all kinds > > > > of abuse including this one. > > > > > > I assume the -e is a bash option? > > > > Any POSIX-compliant shell knows about '-e', bash included. > > Your own rc.local has this shebang: #!/bin/sh -e > > > > > I just rescanned the man page without > > > find a reference other than a test for file -e=exists filename. > > > > dash(1) references it. bash(1) lists '-e' as an option to "set" > > command. > > > > > It is in the shebang line, so what does that do when its in that > > > position. > > > > Quoting bash(1): > > > > -e Exit immediately if a pipeline (which may consist of a single > > simple command), a list, or a compound command (see SHELL GRAMMAR > > above), exits with a non-zero status. > > How about a daemon that never exits, but does report its pid on the next > line when launched with a trailing &
They call such programs a curious perversion in IT usually. Luckily it does not matter for the start-stop-daemon (it can derive pid more straightforward way) nor it does matter to systemd (there are cgroups for that). > I'm also seeing several can't connect to d-bus messages, only ID'd by the > pid. That means whatever its pid is, isn't working. Like I wrote earlier - nothing that you put into rc.local belongs there. I suppose that the thing is written to be launched from the inside the user session, where you have dbus session already. Reco
