Re: T420s 5.9/amd64 fan control?

[Tor Houghton]

On Wed, Apr 06, 2016 at 11:27:11AM -0700, Mike Larkin wrote:
> 
> Someone else recently reported this same issue was fixed by a bios upgrade.
> 
> I'd start there first.
> 

Aha. Yes, the dmesg tells me it's from 2011. Ok; thanks for the tip.

Tor

T420s 5.9/amd64 fan control?

[Tor Houghton]

Hello,

5.9 installed just fine, but I am wondering if there are any means of
controlling the fan (detected as hw.sensors.acpithinkpad0.fan0) - it seems
to be spinning at ~4000rpm, even when X isn't running and the CPU is idle.

I've apmd running, and thought perhaps "apm -A" might do the trick. Appears
to have no effect, so .. looking at acpithinkpad.c, and though there is code
to read the fan speed (high or low) there doesn't seem to be any
corresponding "set fan speed" code...?

Am I out of luck?

Regards,

Tor

Re: Pledge: quota syscall

[Ted Unangst]

Héctor Luis Gimbatti wrote:
> Greetings,
> Ive found that the call at line 536 of quota.c (current) causes abort when
> pledge is required:
> 
> if(quotactl(fs->fs_file, qcmd, id, (char *)>dqblk) != 0)
> 
> Is it necessary to include quotactl (SYS_quotactl) in pledge in order to
> support basecode such as edquota, quota, etc?

I think it would be better to leave pledge out of these utilities for now.

Re: T420s 5.9/amd64 fan control?

[Mike Larkin]

On Wed, Apr 06, 2016 at 07:24:03PM +0200, Tor Houghton wrote:
> Hello,
> 
> 5.9 installed just fine, but I am wondering if there are any means of
> controlling the fan (detected as hw.sensors.acpithinkpad0.fan0) - it seems
> to be spinning at ~4000rpm, even when X isn't running and the CPU is idle.
> 
> I've apmd running, and thought perhaps "apm -A" might do the trick. Appears
> to have no effect, so .. looking at acpithinkpad.c, and though there is code
> to read the fan speed (high or low) there doesn't seem to be any
> corresponding "set fan speed" code...?
> 
> Am I out of luck?
> 
> Regards,
> 
> Tor
> 

Someone else recently reported this same issue was fixed by a bios upgrade.

I'd start there first.

-ml

Re: sendmail mx question

[Markus Rosjat]

Okay with some help from Christoph Viethen I did some testing and 
connfirmed a few things


- sendmail -bt gave me the right order of the mx to talk to
- I couldn't connect to the server with nc
- I couldn't ping the server
- nslookup gave me the correct IP to the server

what really confuses me, and I only did that to have some other tool 
checking if it can connect to the mx in question, is the fact that a 
site like mxtoolbox can talk to the mx.


--
Markus Rosjatfon: +49 351 8107223mail: ros...@ghweb.de

G+H Webservice GbR Gorzolla, Herrmann
Königsbrücker Str. 70, 01099 Dresden

http://www.ghweb.de
fon: +49 351 8107220   fax: +49 351 8107227

Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before 
you print it, think about your responsibility and commitment to the 
ENVIRONMENT

ifconfig down but routing still tries to use the interface's routes

[Doran Mori]

Running 5.9.

I have x.x.141.0/25 that's directly connected. With x.x.141.0/24 reachable
via bgp.

# route -n get x.x.141.13
   route to: x.x.141.13
destination: x.x.141.0
   mask: 255.255.255.128
  interface: em3
 if address: x.x.141.112
   priority: 4 (connected)
  flags: 

# ifconfig em3 down
jawaka# route -n get x.x.141.13
   route to: x.x.141.13
destination: 66.117.141.0
   mask: 255.255.255.128
  interface: em3
 if address: x.x.141.112
   priority: 4 (connected)
  flags: 

I see the UP flag is removed but it has no effect.

# ping x.x.141.13
PING x.x.141.13 (x.x.141.13): 56 data bytes
ping: sendto: Network is down

I would expect this route to be used instead:
# route -n get x.x.141.0/24
   route to: x.x.141.0
destination: x.x.141.0
   mask: 255.255.255.0
gateway: x.x.144.154
  interface: em2
 if address: x.x.144.153
   priority: 48 (bgp)
  flags: 

I searched the archives but didn't see this specific case mentioned. Can
someone enlighten me?

dmo

ports(7) has a 404 link

[Solène Rapenne]

Hi

Dead link in ports(7)


Index: ports.7
===
RCS file: /cvs/src/share/man/man7/ports.7,v
retrieving revision 1.106
diff -u -p -r1.106 ports.7
--- ports.7 24 Nov 2015 21:27:03 -  1.106
+++ ports.7 6 Apr 2016 12:16:25 -
@@ -743,7 +743,7 @@ List of users and groups created by port
 The
 .Ox
 Ports System:
-.Lk http://www.openbsd.org/faq/ports/ports.html
+.Lk http://www.openbsd.org/faq/faq15.html
 .Pp
 The
 .Ox

Re: Gogs PostgreSQL

[Robert Klein]

Hi,
Predrag Punosevac  wrote:

> Hi Misc,
> 
> Is anybody running Gogs 
> 
> https://gogs.io/
> 
> in production on OpenBSD using PostgreSQL as a backend. Any chance to
> share the installation/configuration notes with me?

Here are my notes (for both mariadb and postgresql from different
tests).  Note that, contrary to the gogs instructions for postgresql
the database user `git' is not allowed to create databases and the
`gogs_production' database is created by the database's `postgres' user.

Please don't copy and paste that won't work: some interaction is
needed.  I used Yuki Izumi's rc script but did not run gogs in
the build directory.

I edited the notes, please be aware there may be some mistyped
instructions.

Best regards
Robert


# gogs needs bash for some hooks.
pkg_add bash go git mariadb-server postgresql-server zip unzip-6.0p9
# zip for `make pack'


## MariaDB setup
cat >> /etc/login.conf <> /etc/login.conf < gogs/custom/conf/app.ini /etc/rc.d/gogs <

To all gophers whom it may concern

[Yestin Harrison]

If anyone was holding off on developing http-serving Go apps on 5.9 or 
recent -current because of a lack of syscall.Pledge to go with your 
syscall.Chroot and syscall.Setuid, I'm pleased to present a library that 
provides native-Go access to pledge(2). It is located at 
https://github.com/ylih/extrasys and its Go package import path is 
"ylh.io/extrasys". Now you can privilege-drop your Go apps to your 
heart's content.

Re: Should random.seed on shutdown be saved a little later?

[Kevin Chadwick]

> > > Whilst likely not a major issue. I also started to wonder whilst
> > > reading man rc.shutdown, if a daemon or other process could potentially
> > > use /dev/urandom between saving the seed and shutdown so could/should
> > > the random.seed be saved a little later after /etc/rc.shutdown runs?
> > 
> > 
> > that doesn't matter.  
> 
> Ok cool no should, but is there any reason not to make it easier for RO
> setups by moving the random.seed to after rc.shutdown runs? Would a
> patch for rc and the man page be welcome?

Index: src/etc/rc
===
RCS file: /cvs/src/etc/rc,v
retrieving revision 1.474
diff -u -p -r1.474 rc
--- src/etc/rc  29 Dec 2015 19:41:24 -  1.474
+++ src/etc/rc  6 Apr 2016 16:09:18 -
@@ -211,13 +211,6 @@ FUNCS_ONLY=1 . /etc/rc.d/rc.subr
 _rc_parse_conf
 
 if [[ $1 == shutdown ]]; then
-   if echo 2>/dev/null >>/var/db/host.random || \
-   echo 2>/dev/null >>/etc/random.seed; then
-   random_seed
-   else
-   echo warning: cannot write random seed to disk
-   fi
-
# If we are in secure level 0, assume single user mode.
if (($(sysctl -n kern.securelevel) == 0)); then
echo 'single user: not running shutdown scripts'
@@ -234,6 +227,13 @@ if [[ $1 == shutdown ]]; then
fi
 
[[ -f /etc/rc.shutdown ]] && sh /etc/rc.shutdown
+   fi
+
+   if echo 2>/dev/null >>/var/db/host.random || \
+   echo 2>/dev/null >>/etc/random.seed; then
+   random_seed
+   else
+   echo warning: cannot write random seed to disk
fi
 
# Bring carp interfaces down gracefully.


Index: src/share/man/man8/rc.shutdown.8
===
RCS file: /cvs/src/share/man/man8/rc.shutdown.8,v
retrieving revision 1.14
diff -u -p -r1.14 rc.shutdown.8
--- src/share/man/man8/rc.shutdown.814 Jul 2014 09:14:11 -
1.14 +++ src/share/man/man8/rc.shutdown.86 Apr 2016 16:06:10 -
@@ -49,9 +49,7 @@ This document details the actions taken 
 .Xr rc 8
 in such an instance.
 .Pp
-Firstly it saves random data for reseeding the kernel random number
-generator during the next boot.
-It then stops any daemons
+Firstly it stops any daemons
 defined in the
 .Va pkg_scripts
 variable in
@@ -65,6 +63,9 @@ then runs
 .Nm .
 The administrator should place in this file
 any commands they wish to have executed during shutdown.
+.Pp
+Next it saves random data for reseeding the kernel random number
+generator during the next boot.
 .Pp
 Finally, all
 .Xr carp 4


-- 

KISSIS - Keep It Simple So It's Securable

Re: sendmail mx question

[Markus Rosjat]

Hi Craig,

yeah my server is fine in general but maybe the other adin just has some 
sort of own ways to blacklist so I might be on there list. I'll check 
this too but it seems it could be a routing problem to since the other 
mx sometimes talk and sometimes not (checked from other location to 
connect and I was able to connect only once).


So I'll give the "nice" guy on the other and of the line a last hint and 
then I just leave it because I pretty much ruled all things that could 
go wrong out on my end.


Regards

Am 06.04.2016 um 16:25 schrieb Craig Skinner:

Hi Markus,

On 2016-04-06 Wed 09:29 AM |, Markus Rosjat wrote:

Okay with some help from Christoph Viethen I did some testing and connfirmed
a few things

- sendmail -bt gave me the right order of the mx to talk to
- I couldn't connect to the server with nc
- I couldn't ping the server
- nslookup gave me the correct IP to the server

what really confuses me, and I only did that to have some other tool
checking if it can connect to the mx in question, is the fact that a site
like mxtoolbox can talk to the mx.



They've probably got your IP address in a blacklist of some sort.
Check your mail server's IP address on http://multirbl.valli.org/lookup/
(You might need to be delisted.)

Otherwise, try traceroute (-I) from your mail server to theirs to find
where the trail ends.

Then contact them by phone/fax/freemail with your problem report.

Cheers.



--
Markus Rosjatfon: +49 351 8107223mail: ros...@ghweb.de

G+H Webservice GbR Gorzolla, Herrmann
Königsbrücker Str. 70, 01099 Dresden

http://www.ghweb.de
fon: +49 351 8107220   fax: +49 351 8107227

Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before 
you print it, think about your responsibility and commitment to the 
ENVIRONMENT

Re: sendmail mx question

[Craig Skinner]

Hi Markus,

On 2016-04-06 Wed 09:29 AM |, Markus Rosjat wrote:
> Okay with some help from Christoph Viethen I did some testing and connfirmed
> a few things
> 
> - sendmail -bt gave me the right order of the mx to talk to
> - I couldn't connect to the server with nc
> - I couldn't ping the server
> - nslookup gave me the correct IP to the server
> 
> what really confuses me, and I only did that to have some other tool
> checking if it can connect to the mx in question, is the fact that a site
> like mxtoolbox can talk to the mx.
> 

They've probably got your IP address in a blacklist of some sort.
Check your mail server's IP address on http://multirbl.valli.org/lookup/
(You might need to be delisted.)

Otherwise, try traceroute (-I) from your mail server to theirs to find
where the trail ends.

Then contact them by phone/fax/freemail with your problem report.

Cheers.
-- 
Bizarreness is the essence of the exotic.

Re: Should random.seed on shutdown be saved a little later?

[Kevin Chadwick]

> > Whilst likely not a major issue. I also started to wonder whilst
> > reading man rc.shutdown, if a daemon or other process could potentially
> > use /dev/urandom between saving the seed and shutdown so could/should
> > the random.seed be saved a little later after /etc/rc.shutdown runs?  
> 
> 
> that doesn't matter.

Ok cool no should, but is there any reason not to make it easier for RO
setups by moving the random.seed to after rc.shutdown runs? Would a
patch for rc and the man page be welcome?

-- 

KISSIS - Keep It Simple So It's Securable