Re: CyberPower cp1500PPFCLCD
On 11/14/22 3:35 AM, Stuart Henderson wrote: That is just for APC UPS. I know it's supposed to be just for APC UPSes, but it's my understanding that apcupsd works, at least for some, CyberPower UPSes.
Re: CyberPower cp1500PPFCLCD
On 11/13/22 12:56 PM, Peter Fraser wrote: My sensorsd.conf contains hw.sensors.upd0.percent0:low=99.00%:command=/etc/ups-shutdown %2 The 99.00% was to allow me to test it easily As far as I could tell there is no way to ask sensorsd to only run a program when the UPS is not charging and the % left is less than a value. At this point one of two things happened. Either then upd0 values disappear from sysctl or the system dies with no messages, and I have to do a hard reset. Does anyone have any ideas of what is going on and how to fix it. I accidentally sent the below to the op directly before. Sorry about that. I just wanted to make sure you know about apcupsd [1]. It may work for your UPS, even though it's not APC branded. It's in the OpenBSD repos. http://www.apcupsd.org/
Re: Syncthing permissions question
On 10/26/22 9:38 PM, Jag Talon wrote: I'm unfamiliar with permissions in general i find midnight commander's representation of permissions [1] to be helpful when first learning about them. You might check that out going forward. 1. f9->right arrow to "file"->down arrow to "chmod".
Re: How do I report a kernel panic occuring on install media?
On 4/13/22 3:01 AM, misc.99...@aleeas.com wrote: As far as I remember the CPU is only 32-bit capable. But outputs I gathered from Linux is telling me otherwise (given below). i don't know enough about this cpu, so i'm going to bow out now. i just thought it was a simple accident. sorry if i sent you on a wild goose chase.
Re: How do I report a kernel panic occuring on install media?
On 4/12/22 9:39 PM, misc.99...@aleeas.com wrote: I'm trying to boot OpenBSD 7.0 i386 image (sha256: 2423307414df1800537063b3cafd9ae788b46711074b7f94d855c8a3de622f51) from a USB flash drive on HP Mini, Intel Atom N2600 1.60 GHz machine It sounds like you're trying to use the 32bit OpenBSD installer for a 64bit cpu. In that case, you would want the AMD64 installer.
Re: Used Cores / Threads CPU E3-1230 V2
On 4/5/22 6:29 PM, Heiko wrote: Hello List, I use a Xeon(R) CPU E3-1230 V2 on bios0: Supermicro X9SCL/X9SCM This is a 4 Core 8 Threads cpu. In dmesg, cpu0 to cpu7 are displayed as follows: cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU E3-1230 V2 @ 3.30GHz, 3300.47 MHz, 06-3a-09 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR, ... MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: apic clock running at 100MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE cpu at mainbus0: not configured Now I'm a bit confused about the views in top and htop. top shows me cpu0 to cpu3. htop shows me 1 to 8, but 5 to 8 is shown as "offline" It is (uname -a): OpenBSD user@host 7.1 GENERIC.MP#461 amd64 and some kernels before. Now my question, in "top" only the physical cores are displayed. In "htop" all that are also shown in dmesg. But why are the cpu4 to cpu8 displayed as "offline". Is really only cpu0 to cpu3 used and not cpu4 to cpu7, how can I interpret that correctly? Thank you for the clarification in advance. /Heiko It is my understanding that HT/SMT is disabled in OpenBSD by default. A web search about that should give you more info.
Re: issue with move to php8 as default
rc.conf.local cool! thanks! Just in case it helps someone in the future, i added: php74_fpm_flags=-y /etc/php74-fpm.conf php80_fpm_flags=-y /etc/php80-fpm.conf to rc.conf.local, which each reference listen = /var/www/run/php74/php-fpm.sock and listen = /var/www/run/php80/php-fpm.sock respectively. This works.
Re: issue with move to php8 as default
The php-fpm ports default to using /etc/php-fpm.conf. If you are running both php74_fpm and php80_fpm together then you must change this default for at least one of them and point it at its own configuration file e.g. php74_fpm_flags=-y /etc/php-fpm-7.4.conf Nothing has changed in this respect. Thanks. i'm guessing that goes in the port source code/make file. i'll check it out. I think it would be nice if each PHP version defaulted to using it's own versioned config file since OpenBSD already packages three versions, unless there's some downside i'm not thinking of. This would make OpenBSD even more attractive and convenient for php app hosting by default. Just for maintainer's consideration... Thanks for all the responses. I wasn't getting any of them through claws mail for some reason. Moved this account to tbird now. Thanks, ITwrx
Re: issue with move to php8 as default
On Wed, 30 Mar 2022 09:30:39 -0500 ITwrx wrote: > > Hi ITwrx > > > > you will need to check your rc.conf.local and update it to start up > > the php8.0 fpm > > > > it is possible (im not saying it is recommended) but it is possible > > to run different versions of php fpm (with different socket files) > > for different applications on the same server ... > > but it sounds like you just need to remove the php7.4 fpm line in > > your rc.conf.local and replace it with a line that would startup > > your php8 fpm > > > > I hope this helps, > > > > > > > > On Mon, 28 Mar 2022 at 20:10, ITwrx wrote: > > > > > I'm running php7.4 and php8 at the same time on an OpenBSD 7.0 > > > machine i'm testing as a web server. I'm pretty sure they were > > > both starting up fine until yesterday (it's been a while) after i > > > updated with pkg_add -u and syspatch. Now, php8 fails to start > > > with: > > > > > > ERROR: Another FPM instance seems to already listen on > > > /var/www/run/php-fpm.sock > > > ERROR: FPM initialization failed > > > > > > This seems to be due to the fact that php8.0 became the new > > > default, but it looks like php74 is still trying to use > > > php-fpm.sock instead of php-fpm74.sock, or whatever it's supposed > > > to be called once it's not the default anymore. > > > > > > Am i missing something, or is this a bug? If the latter, is this > > > email sufficient to get it looked at, or i would need to report it > > > more formally? > > > > > > Thanks, > > > ITwrx > > > > > > > > > > This was accidentally sent to Tom Smyth directly, previously. Sorry > about that. I'm new to Claws mail and using it just for mailing lists, > and didn't think to check how it was handling replies. > > Thanks for your reply. > > If i get rid of php74_fpm it will just start php8 as default and only > php version, which is not what i want. It seems to me that the socket > file used to respect the php version by creating php-fpm74.sock, > php-fpm80.sock, etc, and not just create "php-fpm.sock", causing > a collision. Or maybe the non-default php sockets use the version > number but not the default version's socket? Maybe when php80 became > the default, php74 was supposed to be modified to create > php74-fpm.sock since it's not the default anymore, but that was > overlooked due to the assumption that people should just use one or > the other? Am i imagining that, or this new behavior is a bug? What > is responsible for designating what the socket is named? is it > configurable, or hardcoded in the package/port source? > > I already had/have the /etc/php-7.4/php-fpm.conf and > /etc/php-8.0/php-fpm.conf files configured with > "www/run/php74-fpm.sock" and "www/run/php80-fpm.sock" respectively and > i believe that was working prior to the update, so they already know > what socket to listen on, but the socket files themselves are not > being created properly now. > > thanks, > ITwrx it seems both php versions only expect to use /etc/php-fpm.conf and therefore i can't specify different folders by version for the socket. Is there no way to name separate php-fpm.conf files per version so that this will work? Seems like a missed opportunity for OpenBSD and users when 3 versions are already packaged.
issue with move to php8 as default
> Hi ITwrx > > you will need to check your rc.conf.local and update it to start up > the php8.0 fpm > > it is possible (im not saying it is recommended) but it is possible > to run different versions of php fpm (with different socket files) > for different applications on the same server ... > but it sounds like you just need to remove the php7.4 fpm line in your > rc.conf.local and replace it with a line that would startup your > php8 fpm > > I hope this helps, > > > > On Mon, 28 Mar 2022 at 20:10, ITwrx wrote: > > > I'm running php7.4 and php8 at the same time on an OpenBSD 7.0 > > machine i'm testing as a web server. I'm pretty sure they were both > > starting up fine until yesterday (it's been a while) after i > > updated with pkg_add -u and syspatch. Now, php8 fails to start with: > > > > ERROR: Another FPM instance seems to already listen on > > /var/www/run/php-fpm.sock > > ERROR: FPM initialization failed > > > > This seems to be due to the fact that php8.0 became the new default, > > but it looks like php74 is still trying to use php-fpm.sock instead > > of php-fpm74.sock, or whatever it's supposed to be called once it's > > not the default anymore. > > > > Am i missing something, or is this a bug? If the latter, is this > > email sufficient to get it looked at, or i would need to report it > > more formally? > > > > Thanks, > > ITwrx > > > > > This was accidentally sent to Tom Smyth directly, previously. Sorry about that. I'm new to Claws mail and using it just for mailing lists, and didn't think to check how it was handling replies. Thanks for your reply. If i get rid of php74_fpm it will just start php8 as default and only php version, which is not what i want. It seems to me that the socket file used to respect the php version by creating php-fpm74.sock, php-fpm80.sock, etc, and not just create "php-fpm.sock", causing a collision. Or maybe the non-default php sockets use the version number but not the default version's socket? Maybe when php80 became the default, php74 was supposed to be modified to create php74-fpm.sock since it's not the default anymore, but that was overlooked due to the assumption that people should just use one or the other? Am i imagining that, or this new behavior is a bug? What is responsible for designating what the socket is named? is it configurable, or hardcoded in the package/port source? I already had/have the /etc/php-7.4/php-fpm.conf and /etc/php-8.0/php-fpm.conf files configured with "www/run/php74-fpm.sock" and "www/run/php80-fpm.sock" respectively and i believe that was working prior to the update, so they already know what socket to listen on, but the socket files themselves are not being created properly now. thanks, ITwrx
issue with move to php8 as default
I'm running php7.4 and php8 at the same time on an OpenBSD 7.0 machine i'm testing as a web server. I'm pretty sure they were both starting up fine until yesterday (it's been a while) after i updated with pkg_add -u and syspatch. Now, php8 fails to start with: ERROR: Another FPM instance seems to already listen on /var/www/run/php-fpm.sock ERROR: FPM initialization failed This seems to be due to the fact that php8.0 became the new default, but it looks like php74 is still trying to use php-fpm.sock instead of php-fpm74.sock, or whatever it's supposed to be called once it's not the default anymore. Am i missing something, or is this a bug? If the latter, is this email sufficient to get it looked at, or i would need to report it more formally? Thanks, ITwrx
Re: disklabel partition auto allocation problem
On 6/9/21 11:40 AM, electronmuontau neutrino wrote: > disklabel in OpenBSD 6.9 doesn't seem to be allocating partition sizes > correctly according to the actual size of my OpenBSD partition. maybe this will help you: http://daemonforums.org/showthread.php?t=11748
Re: httpd - conditional redirects
On 4/28/21 7:45 PM, theni...@gmail.com wrote:
> Hope I'm putting this in the appropriate mailing list.
>
> A minor (I hope) potential feature request for httpd:
>
> I wish to redirect clients not from a certain IP (e.g. my public IP at
> home) to a different location, temporarily. The purpose of this is to
> allow setting up a "maintenance" page so that I can properly test my
> site with a piece of mind before actually making it available to
> other visitors. I personally consider this a crucial ability.
>
> The way I would usually solve it via Apache is to use RewriteCond and
> RewriteRule. For httpd, however, it could suffice to implement a simple
> "redirect" directive maybe:
>
> redirect [not] to
>
> I could then accomplish what I want using two location blocks:
>
> location match "^/maintenance.html$" {
> root "/htdocs/example.com/maintenance"
> }
> location match ".*" {
> redirect not my.ho.me.ip to scheme://host/maintenance.html
> }
>
> I warmly welcome other ideas to accomplish this as well.
>
> Thanks.
>
one way to accomplish this is to put your testing site on a subdomain
and the maint page on the main domain. only allow your ip to the testing
subdomain. allow all to maint domain. when done testing, swap things
out. there may be a way to block/allow with existing rewrite
rules/features, but i'm not very experienced with httpd and relayd, so i
would have to look it up, and i'm too lazy for that right now. :)
