Date: Wed, 4 Feb 2004 19:58:12 +1100 (EST) From: Edwin Groothuis <edwin@mavetju.org> To: FreeBSD-gnats-submit@FreeBSD.org Subject: bin/62334: vipw doesn't see changes if re-edit for the second time Message-ID: <20040204085812.EB9376A7101@k7.mavetju> Resent-Message-ID: <200402040900.i1490aes061519@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 62334 >Category: bin >Synopsis: vipw doesn't see changes if re-edit for the second time >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Feb 04 01:00:35 PST 2004 >Closed-Date: >Last-Modified: >Originator: Edwin Groothuis >Release: FreeBSD 4.8-RELEASE i386 >Organization: >Environment: System: FreeBSD k7.mavetju 4.8-RELEASE FreeBSD 4.8-RELEASE #1: Mon Jan 5 18:59:31 EST 2004 edwin@k7.mavetju:/usr/src/sys/compile/k7 i386 Also seen on -current of January 26th 2004 >Description: If you run "vipw", make a change but make a mistake, and quit the editor, you are warned about the mistake and are send back to the editor. If you then don't save the file, but just quit, vipw will say "no changes" and not update the old /etc/passwd but just quit. >How-To-Repeat: vipw edit an entry but make a mistake (remove a : too much) :wq choose to re-edit :q! vipw now says "vipw: no changes made", which is true with regarding to the broken version of passwd which was just edited, but not with regarding to the original version of passwd which was edited. I expected to get thrown back into vi to fix the passwd file, or at least get the option of aborting or going on. >Fix: - >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040204085812.EB9376A7101>