On Mon, Oct 30 2017, Lari Rasku <[email protected]> wrote: > Oct 27 snapshot, amd64. > > I have the following binds in /etc/ksh.bindings: > > bind '^[[7~'=beginning-of-line > bind '^[[8~'=end-of-line > bind '^[[2~'=no-op # insert > bind '^[[3~'=delete-char-forward > > I load the file in /etc/profile by setting the ENV variable: > > export ENV=/etc/ksh.bindings > > This causes /usr/libexec/security to spit out the following warnings on > every run: > > /bin/ksh: /etc/ksh.bindings[1]: bind: cannot bind, not a tty > /bin/ksh: /etc/ksh.bindings[2]: bind: cannot bind, not a tty > /bin/ksh: /etc/ksh.bindings[3]: bind: cannot bind, not a tty > /bin/ksh: /etc/ksh.bindings[4]: bind: cannot bind, not a tty > > Which earns me pointless daily(8) mail. > > The cause seems to be that security(8) tries to run an interactive shell > without a tty, but I expect the devs know better if that's really > necessary,
ENV is checked on purpose. Whether it should use sh -i is another question. > or how it might be worked around. case $- in *i*) ...;; esac See /etc/ksh.kshrc. -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
