17 Feb
2012
17 Feb
'12
2:13 p.m.
On Fri, Feb 17, 2012 at 03:03:21PM +0100, SanskritFritz wrote:
On Fri, Feb 17, 2012 at 12:18 PM, Lukas Fleischer <archlinux@cryptocrack.de> wrote:
a) You're not using bash (e.g. running rc.d(8) in sh(1)/$whatever). b) You built bash manually and disabled process substitution support. c) You're running bash in POSIX mode. d) Something else happened.
e) Someone hacked into your system and changed the shebang of all daemon scripts to "#!/bin/sh".
Maybe f) Your default shell is not bash?
That doesn't matter unless he invokes the "rc.d" script in a pretty stupid way. The most likely reason is that the script in question has a "#!/bin/sh" shebang (even though the OP claimed that it happens with all daemon scripts)...