happy birthday theo
here's wishing theo deraadt a very happy birthday. wish you many more years of producing great software and being cantankerous. :p have a great day today and an amazing year ahead. -mayuresh
Re: best place to put export variables
"Best" depends on you and your system and how you use your system. (Are you the sole user of your system? Do you share access? Under what conditions? How much storage does your system have? Etc..) Conceptually, $HOME/.login is a fine place to define an environment variable, though there's ways of using the system which would bypass that definition. Conceptually, you might have situations where you want to bypass your cache home definition, though of course many people would not want such a thing. Conceptually, the system should work just fine with the default behavior (which uses $HOME/.cache if I remember right). And maybe that's the best for you. Ideally, you should be the person who determines the best choices for you, and you should be looking for information which is relevant to whatever is unusual about your situation. -- Raul On Wed, May 18, 2022 at 6:51 PM Mihai Popescu wrote: > > Hello, > > I want to export XDG_CACHE_HOME variable used by Xorg. > What is the best place (file or ?) to export this variable? > > I remember i used some file to export a long time ago PS1 variable. > Should I use ~/.login file or is it a better way to export this xorg variable? > > OpenBSD amd64 here, snapshots install. > > Thank you. >
best place to put export variables
Hello, I want to export XDG_CACHE_HOME variable used by Xorg. What is the best place (file or ?) to export this variable? I remember i used some file to export a long time ago PS1 variable. Should I use ~/.login file or is it a better way to export this xorg variable? OpenBSD amd64 here, snapshots install. Thank you.
Strange relayd(8) logs meaning?
Hello, I have relayd(8) in front of nginx(8) to render a local Nextcloud instance. From time to time, the Nextcloud client fails saying "Host not found" which has no sense. The whole workstation still accesses the network and can resolve anything. relayd(8) listens on em1 IP and uses http protocol. nginx(8) listens on localhost. I have noted that relayd(8) writes such following entries in syslog when the Nextcloud client fails: May 18 16:45:54 server relayd[39533]: relay https_lan_relay, session 2816 (1 active), nextcloud, 192.168.0.48 -> :9081, done, PROPFIND -> 127.0.0.1:9081; PROPFIND; PROPFIND; PROPFIND; PROPFIND; PROPFIND; PROPFIND; REPORT; May 18 16:46:42 server relayd[97191]: relay https_lan_relay, session 3091 (1 active), nextcloud, 10.15.5.76 -> :9081, done, GET -> 127.0.0.1:9081; GET; PROPFIND; GET; GET; PROPFIND; GET; Are such logs (the HTTP commands pipelined with ;) indicating something weird happening on relayd or isn't it a clue for anything ; and I must dig somewhere else? Thank you, Joel C.
Re: Problems with bsd.rd upgrade and FDE.
Nicola Dell'Uomo wrote: > From a couple of weeks I've been noticing these problems when I upgrade from > bsd.rd: > > - after installing all verified .tgz files and making device nodes & > fw_update my system reports as follows: 'Failed to install bootblocks. You > will not be able to boot OpenBSD from sd1.' sd1 is my FDE volume, which after > this message boots; > - after this upgrade my system boots GENERIC (and not GENERIC.MP) kernel; top > confirms I'm runnig with just one cpu; > - in order to be back to MP I have to expressly load bsd.mp at prompt; or > compile my own kernel (GENERIC.MP), install and reboot. > > Am I missing something or should I file a bug? What kind of question is that? You could skip filing a bug, and we can skip looking into it. There are a few people who have mentioned issues, and thus far they have been providing incredibly bad reports, as in, they have *NO LOG* of the upgrade, and they assume we should be able to read tea leaves or something. As for "FDE", whatever that means! There are numerous ways to setup such systems because the installer doesn't do it native, and I believe MANY PEOPLE have set it up using bizzare configurations, and if bsd.rd doesn't know what is going on.. I want to also mention I remain bewildered that we provide source, that the install script is on the install media, that the install media can be mounted, that the install script can be edited to make it more verbose to help in debugging UNDESCRIBED configurations WE DON'T HAVE, but hey self-help seems to be a completely foreign concept.
Re: Telegraf returns an error in OpenBSD 7.1
On 12/05/2022 18:38, Zé Loff wrote:
On Thu, May 12, 2022 at 05:51:34PM +0200, Carlos López Martínez wrote:
On 12/05/2022 17:40, Zé Loff wrote:
On Thu, May 12, 2022 at 03:40:36PM +0200, Carlos López Martínez wrote:
Hi all,
Does telegraf package works under OpenBSD 7.1? I have installed from package
binaries and returns the following error:
+ daemon=/usr/local/bin/telegraf
+ daemon_logger=daemon.info
+ daemon_user=_telegraf
+ . /etc/rc.d/rc.subr
+ _rc_actions=start stop restart reload check
+ readonly _rc_actions
+ [ -n ]
+ _name=telegraf
+ _rc_check_name telegraf
+ [ -n @(#)PD KSH v5.2.14 99/07/13.2 ]
+ [ -n /usr/local/bin/telegraf ]
+ unset _RC_DEBUG _RC_FORCE
+ getopts df c
+ shift 0
+ _RC_RUNDIR=/var/run/rc.d
+ _RC_RUNFILE=/var/run/rc.d/telegraf
+ _rc_do _rc_parse_conf
+ rc_reload_signal=HUP
+ rc_stop_signal=TERM
+ eval _rcflags=${telegraf_flags}
+ _rcflags=
+ eval _rclogger=${telegraf_logger}
+ _rclogger=
+ eval _rcrtable=${telegraf_rtable}
+ _rcrtable=
+ eval _rctimeout=${telegraf_timeout}
+ _rctimeout=
+ eval _rcuser=${telegraf_user}
+ _rcuser=
+ getcap -f /etc/login.conf.d/telegraf:/etc/login.conf telegraf
+ > /dev/null
+ 2>&1
+ daemon_class=telegraf
+ [ -z ]
+ daemon_rtable=0
+ [ -z ]
+ daemon_timeout=30
+ [ -z _telegraf ]
+ [ -n -o start != start ]
+ [ -n ]
+ [ -n ]
+ [ -n ]
+ [ -n ]
+ [ -n ]
+ [ -n ]
+ readonly daemon_class
+ unset _rcflags _rclogger _rcrtable _rctimeout _rcuser
+ eval echo /usr/local/bin/telegraf
+ echo /usr/local/bin/telegraf
+ pexp=/usr/local/bin/telegraf
+ rcexec=su -fl -c telegraf -s /bin/sh _telegraf -c
+ id -R
+ [ 0 -eq 0 ]
+ rc_bg=YES
+ rc_reload=NO
+ rc_cmd start
telegraf(failed)
Trying to execute as root from shell:
root@obsdnode01:/etc/login.conf.d# telegraf -h
2022/05/12 13:39:49 mmap: cannot allocate memory
Any idea?
--
Best regards,
C. L. Martinez
I'm running telegraf on several amd64 7.1 (both -stable and recent-ish
-current) machines. I also get the mmap error when running by hand,
but it works fine with the default rc script:
$ cat /etc/rc.d/telegraf
#!/bin/ksh
daemon="/usr/local/bin/telegraf"
daemon_logger="daemon.info"
daemon_user="_telegraf"
. /etc/rc.d/rc.subr
rc_bg=YES
rc_reload=NO
rc_cmd $1
Cheers
Zé
Uhmm ... In my case, it fails using rc script also ... and it is the same as
yours ...
/etc/login.conf.d/telegraf sets the datasize at 8G. You might not have
as much.
In my case, it fails as a regular user -- because they aren't allowed to
allocate that much -- but works using the rc script because in that case
the daemon is ran as _telegraf, which has its own login class, with the
appropriate values.
I have tried using a simple configuration without configuring inputs,
only outputs, and it doesn't work either (neither manually nor by rc
script).
At this point I have no idea why it fails. I have other virtual machines
with FreeBSD with 1 GB of ram allocated with multiple configured inputs
and it works without problems
--
Best regards,
C. L. Martinez
