You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 7090 Reporter:@Chris00 Status: acknowledged (set by @damiendoligez on 2017-04-13T11:15:00Z) Resolution: open Priority: low Severity: feature Category: otherlibs Monitored by:@Chris00
Bug description
On Windows, there are many alternatives¹ for xhown (I haven't investigated further but they clearly indicate that a syscall must exist). Maybe it would make sense to have "higher level" functions that set ownership for named users (using pwd.h on the Unix side)?
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc.
Original bug ID: 7090
Reporter: @Chris00
Status: acknowledged (set by @damiendoligez on 2017-04-13T11:15:00Z)
Resolution: open
Priority: low
Severity: feature
Category: otherlibs
Monitored by: @Chris00
Bug description
On Windows, there are many alternatives¹ for xhown (I haven't investigated further but they clearly indicate that a syscall must exist). Maybe it would make sense to have "higher level" functions that set ownership for named users (using pwd.h on the Unix side)?
¹ https://serverfault.com/questions/27332/how-to-take-ownership-of-files-from-the-command-line
Additional information
See #349
The text was updated successfully, but these errors were encountered: