On 2019-08-22 12:43, Miroslav Lachman wrote:
>> I run in to something similar from time to time from about 10.x or 8.x (i
>> skipped 9.x)
>> I do not remember exactly what command did the corruption, if it was vipw or
>> chsh or something else to manipulate user database. The fix was easy - run
Miroslav Lachman wrote on 2019/08/22 11:21:
Alan Somers wrote on 2019/08/22 04:07:
Unless, of course your master.passwd file was damaged. But the *.db
files are really just caches for faster access to user data. The
real master file is master.passwd.
The ch* tools typically just change
Alan Somers wrote on 2019/08/22 04:07:
On Wed, Aug 21, 2019 at 7:22 PM Tom Samplonius wrote:
On Aug 21, 2019, at 2:55 PM, Alan Somers wrote:
Today I tried to use chsh to change my shell from bash to fish. The
command completed successfully, but new logins continued to use bash!
On Wed, Aug 21, 2019 at 7:22 PM Tom Samplonius wrote:
>
>
>
> On Aug 21, 2019, at 2:55 PM, Alan Somers wrote:
>
> Today I tried to use chsh to change my shell from bash to fish. The
> command completed successfully, but new logins continued to use bash!
> Investigating, I discovered that
> On Aug 21, 2019, at 2:55 PM, Alan Somers wrote:
>
> Today I tried to use chsh to change my shell from bash to fish. The
> command completed successfully, but new logins continued to use bash!
> Investigating, I discovered that /etc/pwd.db and /etc/spwd.db seem to
> contain 3-4 entries per
Today I tried to use chsh to change my shell from bash to fish. The
command completed successfully, but new logins continued to use bash!
Investigating, I discovered that /etc/pwd.db and /etc/spwd.db seem to
contain 3-4 entries per user. One of those still refers to my old
shell. Worse, if I
