On Mon, 29 Feb 2016 19:34:09 +0530 ash...@freebsd.org (Ashish SHUKLA) wrote:
> On Mon, 29 Feb 2016 14:37:22 +0100, Matthieu Volat <ma...@alkumuna.eu> said: > > > [...] > > > | Hmm, I'll be a bit overwhelmed until thursday, I'll check that... > > Thanks, and I appreciate it. > > [...] > > | Thanks, there was another blocking issue for me yesterday, which is the > ejabberdctl is now in bash. > > | If possible, I'd like to make a patch to (optionally) revert to pure sh, as > I find it a bit sad to go full bash only to read a few parameters... > > | I'll keep you informed > > Thanks in advance, if you could provide the patch. For now, I have updated the > diff to include dependency on bash, which I apparently missed before :/ > > New diff: > > https://people.freebsd.org/~ashish/diffs/ejabberd-16.01-01.diff > sha256 sum: ec71fdd19c752b22271ce6e3f899b966b0017f05fa13532d1decf18478e41b6e > Ok, back on business! My issue with the non-applied patchs is that those were not creates in the files subdir in ejabberd, but in a ejabberd/files subdir. Regarding the pam module installation, it seems to be installed in : /usr/local/lib/erlang/lib/ejabberd-16.01/lib/p1_pam-1.0.0/priv/bin/epam But ejabberd at start will fail with : 2016-03-05 17:52:49.297 [error] <0.394.0> Can't open file "/usr/local/lib/erlang/lib/ejabberd-16.01/lib/erlang/lib/ejabberd-16.01/priv/bin/epam": enoent So I guess it's not installed in the right place? Then, regarding the bash issue, I made some progress, but I still need to test it a bit more to be sure it do not introduce new bugs (it's not much, but I have to see if the kinda simple shell escaping function equivalent I put is enough). -- Matthieu Volat <ma...@alkumuna.eu>
pgpCwzOQ0hyZ_.pgp
Description: OpenPGP digital signature