Project

General

Profile

Actions

Bug #3294

closed

Creating users/groups silently fails on read only filesystem

Added by Phil Sweeney over 12 years ago. Updated about 12 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
User Manager / Privileges
Target version:
Start date:
10/26/2013
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.1
Affected Architecture:
All

Description

Was setting up VPN and following various guides, which included the creation of a group and a user.

I did this, and it was all reported fine, however when I looked at the systemlog it reported an error due to filesystem being readonly.

To clean it up I had to remount as R/W, delete the user and groups, and start over.

Actions #1

Updated by Renato Botelho over 12 years ago

  • Target version set to 2.1.1
  • Affected Architecture All added
  • Affected Architecture deleted (amd64)
Actions #2

Updated by Renato Botelho over 12 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

Applied in changeset commit:b1e5a286bb47d7e4a5b3d589cc27b557b3b13c41.

Actions #3

Updated by Renato Botelho over 12 years ago

Applied in changeset commit:fa757d146c85261b7e90d226c1aecd38089d7e20.

Actions #4

Updated by Ermal Luçi over 12 years ago

The commits are wrong in my opinion!

Why should backend code have to deal with mounting the disk.
I sept a lot of time before on having this cleaned up and now you are adding things back again :)

Actions #5

Updated by Phil Sweeney over 12 years ago

When I reported this I was probably more expecting some error handling to be added so it actually failed properly and told you the error rather than just pretending it worked, but up to you guys :)

Actions #6

Updated by Renato Botelho over 12 years ago

Applied in changeset commit:23b5b16ac6b4107b5321c4e06dfc2b56fa565f20.

Actions #7

Updated by Renato Botelho over 12 years ago

Applied in changeset commit:03e156efac94129f4b152e3561d39279e153aa7a.

Actions #8

Updated by Renato Botelho about 12 years ago

  • Status changed from Feedback to Resolved

It was fixed by commit:8a0ae97fa0e249aa13538103e662aa6191ebde65 and commit:90caf54ebf46763f4856d446ab0aa77259282119

Actions

Also available in: Atom PDF