Bug 151752 - pw.conf(5) doesn't define format for file clearly
Summary: pw.conf(5) doesn't define format for file clearly
Status: Open
Alias: None
Product: Documentation
Classification: Unclassified
Component: Manual Pages (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-26 14:00 UTC by Eir Nym
Modified: 2018-04-11 21:20 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eir Nym 2010-10-26 14:00:18 UTC 
You can see following text in this manual about file format:
===%<---
     Each line in /etc/pw.conf is treated either a comment or as configuration
     data; blank lines and lines commencing with a `#' character are consid-
     ered comments, and any remaining lines are examined for a leading key-
     word, followed by corresponding data.
--->%===
what means "leading key-word, followed by corresponding data"?
for example how anybody can recognize it(common usages):
1) Keyword:Data
2) Keyword:"Data"
3) Keyword:'Data'
4) Keyword=Data
5) Keyword="Data"
6) Keyword='Data'
7) ...

what is delimiter? should/must quotes surround data? which quotes should be used? and so on

Also it is unclear with data for shells keyword: can this line contains any spaces between shell names?

Fix: 

describe format more clearly.
How-To-Repeat: see pw.conf(5) and try to create new pw.conf from scratch without using pw(8) useradd -D command
Comment 1 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 07:58:37 UTC 
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped