Re: VCORE snmp, sysctl hw.sensors

2018-07-23 Thread Philip Guenther
On Mon, Jul 23, 2018 at 3:49 AM Stanley van Dijk  wrote:

> Could anyone help me out with what I'm looking at?
>
> This comes from an snmp mib:
>
> hw.sensors.it0.volt0=1.34 VDC (VCORE_A)
> hw.sensors.it0.volt1=1.92 VDC (VCORE_B)
>
> What is vcore_a and what is vcore_b?
>

Sensor chips are wired up and measure whatever the hell their designers and
users decide.  The it(4) driver is written to expect the voltage sensors on
the chip to measure various inputs, the first two of which are both, to
quote the it(4) manpage, "Core voltage".  What that *really* means is
probably dependent on the motherboard, etc.  So, we do the best we can and
include a label to tell them apart (A vs B) but if you need more details
you'll need to consult the Surely Very Fine and Clear documentation of your
device.


Philip Guenther


Re: Adding New Commands to BGP Looking Glass?

2018-07-23 Thread Denis Fondras
> Do you see where I might've gone wrong? I know that my definition in the .h
> file is wrong, but I'm trying to get this working in baby steps, and perhaps
> I was mistaken but I thought that having a duplicated function would still
> make it appear in the bgplg menu. Is there anything obvious that leaps out
> at you that I'm not seeing?
> 

It is not clear whether you rebuilt ebuilt bgplg or not.
Also mtrace binary needs to be built statically.



VCORE snmp, sysctl hw.sensors

2018-07-23 Thread Stanley van Dijk

Hi all,

Could anyone help me out with what I'm looking at?

This comes from an snmp mib:

hw.sensors.it0.volt0=1.34 VDC (VCORE_A)
hw.sensors.it0.volt1=1.92 VDC (VCORE_B)

What is vcore_a and what is vcore_b?

BR,
Stan



Re: Adding New Commands to BGP Looking Glass?

2018-07-23 Thread MonsieurFugu
Thanks for the reply,

So my first step was getting the "mtrace" source files and copying them into
the "/usr/src/usr.bin/bgplg/" directory, as that is the location of all the
other commands like ping and traceroute. I also added a copy of the
executable into "/var/www/bin/", as the other commands did likewise.
 

Next I configured the "/usr/src/usr.bin/bgplg/bgplg.c" file to add and
define mtrace as a command. The rest of the .c file didn't seem to require
configuring so I left it as is.
 

I finally edited the "/usr/src/usr.bin/bgplg/bgplg.h" file, adding the
mtrace command. I made the mtrace command to be a copy of the ping command
because I wasn't sure what the correct definition of the mtrace command was,
but that shouldn't have stopped the command appearing in the drop down menu
should it?

 

And after doing that it doesn't appear in my bgplg after rebooting and
restarting.
 

Do you see where I might've gone wrong? I know that my definition in the .h
file is wrong, but I'm trying to get this working in baby steps, and perhaps
I was mistaken but I thought that having a duplicated function would still
make it appear in the bgplg menu. Is there anything obvious that leaps out
at you that I'm not seeing?

Thank you for the help.



--
Sent from: http://openbsd-archive.7691.n7.nabble.com/openbsd-user-misc-f3.html



Re: Status of Owncloud?

2018-07-23 Thread Consus
On 16:25 Sun 22 Jul, Rupert Gallagher wrote:
> Nextcloud, a government-funded project to keep your data secure...
> Hold on to your buts, here it comes.

DARPA, OpenBSD... Rings a bell?



Re: Status of Owncloud?

2018-07-23 Thread Marko Cupać
On Sun, 22 Jul 2018 16:25:35 -0400
Rupert Gallagher  wrote:

> Nextcloud, a government-funded project to keep your data secure...
> Hold on to your buts, here it comes.

So,

National governments = bad

I guess as opposed to

Multinational corporations = good

Got it, thanks. 

:D

On a more serious note, I switched to Nextcloud the day it was forked
and never looked back to Owncloud. On FreeBSD though. It introduced
WebRTC videoconferencing via spreed app, also public upload folders, I
like NC more than OC not just because of politics but also because of
features.
-- 
Before enlightenment - chop wood, draw water.
After  enlightenment - chop wood, draw water.

Marko Cupać
https://www.mimar.rs/



support update

2018-07-23 Thread Kihaguru Gathura
0
C Kenya
P Nairobi
T Nairobi
Z P.O. Box 30164-00100
O Weenode
I
A Bishops Road
M e...@weenode.com
U
B +254 706970697
X
N Ultra-secure Enterprise Internet of Things (EIoT). Speciality in web
applications
development with OpenBSD-httpd web server, PostgreSQL DBMS, FastCGI protocol
and C programming language on OpenBSD/ARM platforms.


Re: NextCloud: failed integrity checks

2018-07-23 Thread Gonzalo L. Rodriguez

On [22/07/18] [08:32P], Johan Huldtgren wrote:

On 2018/07/22 15:39, Nicolas Schmidt wrote:

After installation on OpenBSD 6.3 with pkg_add, NextCloud complains about files 
failing the integrity checks. More specifically:

- occ
 * expected hash: 
7e3fce0d7b5c20a7775ed1b548cb2e29bed078d3ca77b01a83d438f671b3d473147d4e8217d2084e17b6fe23a18ba258b11ba60106e23381f1e2889ce14971c4
 * current hash:  
7693eb89c0bc218712d68ec58599efa46e5c3729814e2aad16bf2c0079be7ae1909f072ead7889883c0a89b6c51570800d9e8a71f35866cb4e0c47aeaa5a4b2b

- version.php
 * expected hash: 
4e9046aca4fd8e942ba7bd505374e22ddd500a99b3a46d57d629b99c3132a66206883053f22801894929e51fca307c740062b497d55639bcc9a3154ada3504ff
 * current hash:  
30cd43589fc8ab273fa25e1a477c8cbadb13bac5541daa6d3fa0490a0c2054c2c29a274fd50eec66934a9d9adc541dec8701e7463922d36174478ae3e9a64981

- apps/updatenotification/appinfo/info.xml
 * expected hash: 
bf7983ffe422ba215c04a0069081fab0c78ba81fa40a90cbdd3595182e011fb7f3e0bd1cd14cdea742cafb89f1da001582fe8d560749d98ea540b4ee76dd9898
 * current hash:  
d2984fa816b4cea71e7c09f36a4132e7cb88d357f22e1c795778deccdb4066beaef2876b95d849e6eeae37b879c0f63500b0958a6a61bab1c933736bf135c440


Anybody able to reproduce?


yeah this is known. The port modifies these files to work with OpenBSD
(if you look at the port these files are the ones we patch). You can
work around this by adding this to your config.php

'integrity.check.disabled' => true,

.jh




https://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/www/nextcloud/Makefile?rev=1.17=text/x-cvsweb-markup

--
Sending from my toaster.



Re: NextCloud: failed integrity checks

2018-07-23 Thread Gonzalo L. Rodriguez

On [22/07/18] [07:39P], Nicolas Schmidt wrote:

After installation on OpenBSD 6.3 with pkg_add, NextCloud complains about files 
failing the integrity checks. More specifically:

- occ
* expected hash: 
7e3fce0d7b5c20a7775ed1b548cb2e29bed078d3ca77b01a83d438f671b3d473147d4e8217d2084e17b6fe23a18ba258b11ba60106e23381f1e2889ce14971c4
* current hash:  
7693eb89c0bc218712d68ec58599efa46e5c3729814e2aad16bf2c0079be7ae1909f072ead7889883c0a89b6c51570800d9e8a71f35866cb4e0c47aeaa5a4b2b

- version.php
* expected hash: 
4e9046aca4fd8e942ba7bd505374e22ddd500a99b3a46d57d629b99c3132a66206883053f22801894929e51fca307c740062b497d55639bcc9a3154ada3504ff
* current hash:  
30cd43589fc8ab273fa25e1a477c8cbadb13bac5541daa6d3fa0490a0c2054c2c29a274fd50eec66934a9d9adc541dec8701e7463922d36174478ae3e9a64981

- apps/updatenotification/appinfo/info.xml
* expected hash: 
bf7983ffe422ba215c04a0069081fab0c78ba81fa40a90cbdd3595182e011fb7f3e0bd1cd14cdea742cafb89f1da001582fe8d560749d98ea540b4ee76dd9898
* current hash:  
d2984fa816b4cea71e7c09f36a4132e7cb88d357f22e1c795778deccdb4066beaef2876b95d849e6eeae37b879c0f63500b0958a6a61bab1c933736bf135c440


Anybody able to reproduce?

--Nicolas



Hello,

This is fixed on -current, I disabled the patching on the nextcloud version to
avoid this error.

Cheers.-

--
Sending from my toaster.