01:16:05 [illumos-gate] 9633 cxgbe should not reinvent the bool -- Patrick Mooney 09:34:48 sigh. # prctl -n zone.cpu-shares -v 10 -r -i zone omni 09:34:48 prctl: omni: No controllable process found in task, project, or zone. 09:44:34 prctl -i zone omni has quite normal and expected output, however... 09:47:47 and unfortunately, FSS has no effect on bhyve zone. 18:19:47 tsoome_: As I recall, prctl tries to find a representative process in the zone, which is usually init, but the bhyve brand is a bit wonky (in that it doesn't include the usual tree of processes) 18:20:12 We probably shouldn't be using the agent LWP to effect prctl actions 18:21:10 I wonder if it's also a privileges thing 18:21:22 (not sure what cred the agent operates with...) 20:27:51 hm, thats unfortunate, but if it is really looking for init, then it explains the prctl error. 20:28:48 I havent checked the prctl source (yet?) 20:51:04 [illumos-gate] 17002 want wcslcat(3C) and wcslcpy(3C) -- Robert Mustacchi 20:51:04 [illumos-gate] 17003 fix wcsdup(3C) synopsis -- Robert Mustacchi 21:16:26 since I suspect we might be one of the few people who use it, since AT&T sucked for so long, do we happen to have a potted document for "how to use cscope and be happy"? 21:30:20 jclulow, tsoome_ - is is a privileges thing. In a bhyve zone (at least on OmniOS), bhyve is the zone's init process and it has very limited privileges. In particular it does not have PRIV_SYS_RESOURCE which prctl needs its victim/helper to have. 21:30:44 makes sense 21:31:27 You can still set shares via zonecfg, I just don't know how effective they are. 21:44:04 they are not effective at all with bhyve zone 22:06:22 Is that because most of the CPU usage is system time, and FSS doesn't apply there? 22:06:34 (obviously it should!) 22:11:23 [illumos-gate] 17037 PCI headers missing dependencies -- Robert Mustacchi 22:23:43 I've just never validated it. 22:25:04 I can see reasons it would probably not be great