Not sure how 'answered' this question is since 3rd, but since I was having this problem this week thought I'd pitch in. I used sudo -u cyrus /bin/sh which saves on forgetting to change it back (and has the advantage of not opening anything up further than required in the mean time). On 16/10/15 12:42, Sebastian Hagedorn wrote: > --On 3. Oktober 2015 05:51:42 -0500 Patrick Goetz > <pgoetz@xxxxxxxxxxxxxxx> wrote: > >> I have a question about best practices. I usually have the shell for >> user cyrus set to /bin/false. So to run a reconstruct, I have to change >> this to /bin/bash (or something) first in order to be able to log in as >> cyrus and execute the reconstruct command. >> >> On the other hand, this is only the second time I've had to run >> reconstruct in 12 years of using cyrus. What do most people do about >> this? Is cyrus an ordinary user who can log in by default, or is it >> best practice to have shell /bin/false, as I do with most other daemon >> users? > > We use user cyrus all the time. Not only for reconstruct, but also for > tools like mbexamine, chk_cyrus etc. > > > ---- > Cyrus Home Page: http://www.cyrusimap.org/ > List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ > To Unsubscribe: > https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus ---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
