Re: type of vm.stats.vm.v_vnodepgsin vm.stats.vm.v_swappgsin, vm.stats.vm.v_vnodepgsout vm.stats.vm.v_swappgsout on AMD64 r320730

On Sun, Jul 09, 2017 at 11:15:18PM -0300, Otac??lio wrote: > Dears > > I'm the maintainer of xosview and I'm debugging rather weird behavior > from it in the latest FreeBSD 12 revisions (12.0-CURRENT #0 r320730 > AMD64) . The problem is occurring on the lines responsible for > collecting statis

type of vm.stats.vm.v_vnodepgsin vm.stats.vm.v_swappgsin, vm.stats.vm.v_vnodepgsout vm.stats.vm.v_swappgsout on AMD64 r320730

Dears I'm the maintainer of xosview and I'm debugging rather weird behavior from it in the latest FreeBSD 12 revisions (12.0-CURRENT #0 r320730 AMD64) . The problem is occurring on the lines responsible for collecting statistics about paging. These lines follow: If (pageinfo) { Pageinfo [0]

Re: Getting PID of socket client

On Sun, Jul 09, 2017 at 02:07:06PM +, Johannes Lundberg wrote: > That code gets the child's pid from the fork command. That's is not > available in my case (Wayland client connects to Wayland server via unix > socket). > I can understand the security issue.. hmm will dig further tomorrow.. It

Re: Getting PID of socket client

On Sun, Jul 09, 2017 at 05:43:22PM +0100, David Chisnall wrote: > On 9 Jul 2017, at 14:25, Stefan Ehmann wrote: > > Don't why the structs are not compatible, maybe because: > > "The process ID cmcred_pid should not be looked up (such as via the > > KERN_PROC_PID sysctl) for making security decisi

Re: small patch for /etc/rc.d/nfsd, bugfix or POLA violation?

In message , Rick Macklem writes: > --_002_YTXPR01MB0189F5614497D4FA96A7579ADDA80YTXPR01MB0189CANP_ > Content-Type: text/plain; charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > Hi, > > The attached one line patch to /etc/rc.d/nfsd modifies the script so that i= > t > does no

small patch for /etc/rc.d/nfsd, bugfix or POLA violation?

Hi, The attached one line patch to /etc/rc.d/nfsd modifies the script so that it does not force the nfsuserd to be run when nfsv4_server_enable is set. (nfsuserd can still be enabled via nfsuserd_enable="YES" is /etc/rc.conf.) Here's why I think this patch might be appropriate... (a) - The origin

Re: [bhyve] FreeBSD guest, Handbook, vmrun.sh

09.07.2017 19:08, Benjamin Kaduk пишет: > (BTW, I think there is not agreement as to whether vmrun.sh should > be used in general use, or alternate solutions for VM managemnet.) As a side note: I used the process written at TH... -- WBR, bsam ___ free

[SOLVED] [memstick install] auto-zfs error

08.07.2017 18:56, Boris Samorodov пишет: > Hi All, > > I tied to install a new FreeBSD-amd-12 system from official USB > installation memstick.img. Auto-UFS (GPT) installs fine and the system > boots fine. However, ZFS-Auto install succeeds, but is not loaded. > At the very beginning it gives some

Re: Getting PID of socket client

On 9 Jul 2017, at 14:25, Stefan Ehmann wrote: > > Don't why the structs are not compatible, maybe because: > "The process ID cmcred_pid should not be looked up (such as via the > KERN_PROC_PID sysctl) for making security decisions. The sending process > could have exited and its process ID alre

Re: [bhyve] FreeBSD guest, Handbook, vmrun.sh

09.07.2017 19:08, Benjamin Kaduk пишет: > On Sun, Jul 09, 2017 at 06:58:09PM +0300, Boris Samorodov wrote: >> 09.07.2017 18:48, Boris Samorodov пишет: >>> 09.07.2017 18:37, Benjamin Kaduk пишет: Documentation looks okay, as -I is documented during the install stage, and is not suppo

Re: [bhyve] FreeBSD guest, Handbook, vmrun.sh

On Sun, Jul 09, 2017 at 06:58:09PM +0300, Boris Samorodov wrote: > 09.07.2017 18:48, Boris Samorodov пишет: > > 09.07.2017 18:37, Benjamin Kaduk пишет: > >> > >> Documentation looks okay, as -I is documented during > >> the install stage, and is not supposed to be needed during > >> normal operati

Re: [bhyve] FreeBSD guest, Handbook, vmrun.sh

09.07.2017 18:48, Boris Samorodov пишет: > 09.07.2017 18:37, Benjamin Kaduk пишет: >> On Sun, Jul 09, 2017 at 01:02:26PM +0300, Boris Samorodov wrote: >>> Hi All, >>> >>> I try to create a FreeBSD guest as per TH, section "21.7.2. Creating >>> a FreeBSD Guest". All is good up until the last command

Re: [bhyve] FreeBSD guest, Handbook, vmrun.sh

09.07.2017 18:37, Benjamin Kaduk пишет: > On Sun, Jul 09, 2017 at 01:02:26PM +0300, Boris Samorodov wrote: >> Hi All, >> >> I try to create a FreeBSD guest as per TH, section "21.7.2. Creating >> a FreeBSD Guest". All is good up until the last command at the section. >> When I try to launch the ins

Re: [bhyve] FreeBSD guest, Handbook, vmrun.sh

On Sun, Jul 09, 2017 at 01:02:26PM +0300, Boris Samorodov wrote: > Hi All, > > I try to create a FreeBSD guest as per TH, section "21.7.2. Creating > a FreeBSD Guest". All is good up until the last command at the section. > When I try to launch the installed client, I get: > - > # sh /usr/shar

Re: Problem with make installworld et alii

You need to a build newer than SVN r320652 to fix this .. On 07/09/17 10:43, Filippo Moretti wrote: FreeBSD sting 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r320360: Mon Jun 26 15:49:29 UTC 2017 r...@releng3.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386After compiling world and kernel I can

Problem with make installworld et alii

FreeBSD sting 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r320360: Mon Jun 26 15:49:29 UTC 2017 r...@releng3.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC   i386After compiling world and kernel I cannot make install world with the following error:Fatal error cannot allocate read line in initial threa

Re: Getting PID of socket client

That code gets the child's pid from the fork command. That's is not available in my case (Wayland client connects to Wayland server via unix socket). I can understand the security issue.. hmm will dig further tomorrow.. Thanks for the info! On Sun, 9 Jul 2017 at 15:26, Stefan Ehmann wrote: >

Re: Getting PID of socket client

On 09.07.2017 11:52, Johannes Lundberg wrote: Hi Yeah I forgot to mention the LOCAL_CREDS. It does not return the PID of the client process but i guess it could be expanded to include that instead of adding another option for that. I was only skimming the man page. Didn't see that cmsgcred co

[bhyve] FreeBSD guest, Handbook, vmrun.sh

Hi All, I try to create a FreeBSD guest as per TH, section "21.7.2. Creating a FreeBSD Guest". All is good up until the last command at the section. When I try to launch the installed client, I get: - # sh /usr/share/examples/bhyve/vmrun.sh -c 4 -m 1024M -t tap0 -d guest.img guestname Launchin

Re: Getting PID of socket client

Hi Yeah I forgot to mention the LOCAL_CREDS. It does not return the PID of the client process but i guess it could be expanded to include that instead of adding another option for that. On Sun, Jul 9, 2017 at 11:47 AM, Stefan Ehmann wrote: > On 09.07.2017 10:03, Johannes Lundberg wrote: > >> H

Re: Getting PID of socket client

On 09.07.2017 10:03, Johannes Lundberg wrote: Hi Without altering the client code (i.e. adding sendmsg(credentials)), is there anyway of getting the client PID (or path to binary) using the file descriptor returned by accept() on the server side? Similar to Linux's getsockopt with SO_PEERCRED o

Re: Getting PID of socket client

follow-up Seems like at least OpenBSD implemented SO_PEERCRED which returns a struct sockpeercred. /* Read using getsockopt() with SOL_SOCKET, SO_PEERCRED */ struct sockpeercred { uid_t uid; /* effective user id */ gid_t gid; /* effective group id */ pid_t pid; }; If not anyone is oppose to this

Getting PID of socket client

Hi Without altering the client code (i.e. adding sendmsg(credentials)), is there anyway of getting the client PID (or path to binary) using the file descriptor returned by accept() on the server side? Similar to Linux's getsockopt with SO_PEERCRED option. Thanks!