On 2019-12-31 09:03, White FrosT wrote:
Hi All,
Thanks for the feedback, but I'm not getting there yet.
I tried vipw, but this doesn't work. It was not on my system, installed it with opkg install shadow-vipw. But then running vipw gives me:
vipw: /opt/etc/passwd: No such file or directory
vipw: /opt/etc/passwd is unchanged
Neither does adding a shell to the user (/sbin/nologin) change anything.
Thanks for any additional idea's!
Op di 31 dec. 2019 om 16:54 schreef mlm <m...@sr.unh.edu>:
On 12/30/2019 6:57 PM, Michael Stowe wrote:
On 2019-12-30 12:24, White FrosT wrote:
Dear list,
I have an issue installing backuppc on my new network disk running Linux 4.2.8 ARMv71. I think I have managed all preconditions in perl (v5.28.1) and are ready to install, but I run into an issue with configure.pl [1]. It doesn't let me set the user to run BackupPC with. See the snapshot of the script output below:
--> BackupPC should run as user [backuppc]
getpwnam() says that user backuppc doesn't exist. Please
check the name and verify that this user is in the passwd file.
But the user does exist on my system, see:
[/.../BackupPC-4.3.1] # grep backuppc /etc/passwd
backuppc:x:1000:1000::/share/homes/Backupuser/:
I cannot seem to workaround this problem. Does anyone have any leads?
Thanks a lot!
For what it's worth, I've seen this behavior when shadow hasn't properly been
updated, and it took (takes?) running vipw, then rebooting. YMMV
hi,
Might need an entry where the shell for the user normally goes.
This is what my entry looks like:
backuppc:x:988:983::/var/lib/BackupPC:/sbin/nologin
Mark
What vipw does is set the appropriate locks and prevent corruption while
editing the password file -- under the covers, it's often vi or vim,
anyway. Depending on the platform, this will help trigger the shadow
update (thus my suggestion to use vipw and reboot.) In your case, it
seems the package for vipw doesn't fit with the actual location of
passwd and shadow on your system.
Usually it's best not to directly interact with either file, as a syntax
error can result in accounts not working, instead it is better to use
tools like adduser and passwd. Officially, authconfig (on Linux) is
probably the right way to update whatever files must be coordinated.
You could also just use "passwd backuppc" as root.
Links:
------
[1]
https://u2182357.ct.sendgrid.net/wf/click?upn=rBK8reUlX8Sxr7Iz1fV-2F7Z4Qyz-2FdRVTsykwiKMAKNXGM7CUf5juiBco6vpfp2jz1b2ywz5iHhGuMBRW-2BbsRpyriQYngu5p4EU0mD2E0mSA-2Frx4vGZ-2Fp1CIYOyKiFCqZL8eCJP1ev5gbx6IyiE2BTfJkKHjUD3jIlJreydTMKH-2Bqv1D4uuq43VMS0FaikvKy7VqAPUlvbdOkdgQpiX1eIZsFi7E0PGALblqcD6XODGTiQfrxf2Ww-2BoZuWZLFU2X31h1Hj-2B7GJrneyiX1-2FFvnlxU4I7wTHt8-2BJvq-2BuE5zLiTr95cPfCmN-2BgBrpaxf7gPSN-2BTzAdyMfJ5sUdtb9PCHWXN7wScI7pZTjmfQO3D5gZUHGRa2CsHJXBJdrhwmu7dTlpR03aIEMYoo8yZwBwNj4gjsJIsG7Su84FJqvcIyIpflXD6tIE5sOA4Mgz7Gm4AxuGSD7ZuLRgeSz4BobtEiICRLRUkfskUAU9FWfXtMaQEfFHl4E9e5lVErw-2BKLj8Wso_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91C4PR-2FeKP-2FLdO8ln6xWRdGp8cnfpoH5V4NVAZe-2Fq-2Bh9z0g8pmaI9I2RofHWs4abKW0hMxP-2FYgDt6jpedl3dEvSCf5KgwV1hHupA-2BE700SkCEX7qGo18pLl7f4olsiV1CBAjtJ7lRt4MzjhRnMz1A0wajuroxcwbv1LttHgNJR5ZfPazVedd3kwRdltgqwFurVY
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
