Bug 196609 - install(1) doesn't set correct group when creating parent directories in directory hierarchy
Summary: install(1) doesn't set correct group when creating parent directories in dire...
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 10.1-RELEASE
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-12 17:19 UTC by Anthony Donnelly
Modified: 2025-02-07 06:04 UTC (History)
2 users (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 Anthony Donnelly 2015-01-12 17:19:13 UTC 
When passing -g to install when creating directories with -d, only the top
directory gets the correct group.

For example, if I were to create the direct test/test/test while none of those
exist, using:

install -o root -g wheel -dm755 test/test/test/

Only the the very last directory is set to root:wheel, while the two previous
directories are set to root:amzo.

This is the case even when using sudo. I'm unsure if this is intended, but all
directories created with install(1) should have the owner and group set to the
ones passed.

Environment:
FreeBSD 10.1-RELEASE
Comment 1 Gavin Atkinson freebsd_committer freebsd_triage 2015-01-12 18:46:59 UTC 
Hi,

Due to an issue with the backend FreeBSD Bugzilla database, your original PR and any updates to it since have been lost.  I've recreated the original PR as best as I can, however any attachments and updates you submitted to the PR have been lost.  Please could you resubmit them?

Thanks, and apologies.
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2018-01-08 04:14:26 UTC 
For the following conditions
Product: Base System, Documentation Status: New, Open, In Progress, UNCONFIRMED 
Assignee: Former FreeBSD committer 

Reset to default assignee. Reset status to "Open".
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2025-02-07 06:04:45 UTC 
^Triage: is this still a problem on supported versions of FreeBSD?