00:25:30 <jbo> lw, ping
00:30:30 <HER> is it normal for jail cronjobs to run some seconds late ?
00:31:09 <ek> HER: Not that I've noticed.
00:31:53 <HER> i used this:  * * * * *     /bin/date >> /tmp/cron_minute
00:32:12 <HER> in host it runs each minute at :00
00:32:39 <HER> in jail it varies
00:35:20 <Nux> is there a Freebsd 12 pkg archive/mirror? Need to get picocom for a Pfsense
00:35:51 <jbo> you're running a firewall with an OS that is EOL? o.O
00:35:55 <jbo> these days?!
00:36:52 <Nux> yes, matey, it's how you do it
00:38:20 <HER> everybodys doing and nobody talking about
00:38:52 <Nux> it's some netgate appliance, if I update it pkg goes to hell, can't install anything, it's a longer story
00:39:04 <Nux> anyway, no fbsd 12 archive on the back alleys?
00:39:35 <HER> pkg archive ?
00:39:57 <HER> there is none that i am aware of
00:40:23 <Nux> right, so what are my options here? install fbsd 12, get the ports tree if still available and generate a pkg?
00:40:55 <jbo> picocom has practically no dependencies so you shold be fine
00:41:22 <jbo> I would honestly just get the source from upstream and build outside of ports if it's an emergency situation
00:41:27 <jbo> https://github.com/npat-efault/picocom
00:41:44 <jbo> doesn't even need gmake
00:42:01 <scoobybejesus> HER, i have cron_flags="-J 60" in my bastille jails
00:42:25 <HER> scoobybejesus: oh. i will have to try that
00:42:36 <Nux> I just have this netgate appliance, can't compile anything, will install a freebsd 12 and copy over the binary, cheers jbo
00:42:56 <jbo> why not just install freebsd 14.1 then?
00:43:19 <Nux> netgate pfsense is basedon fbsd 12, just for compat sakes
00:43:25 <jbo> wat
00:43:31 <jbo> wait
00:43:48 <jbo> do you need picocom on the appliance or on another host to interface the appliance over serial?
00:44:01 <Nux> on the actual appliance - so I can interface a switch :)
00:44:45 <jbo> other than why are you not just interfacing the switch from another host... no way that netgate is actively distributing something based on an EOL'd FreeBSD
00:45:31 <Nux> it's an old appliance, jbo , updating it breaks pkg, it gets complicated, I just want picocom and my desktop icons back in penis shaped as they were before
00:46:10 <jbo> alrighty
00:46:22 <jbo> if it helps: I used to run pfsense myself for many years until I eventually just ditched it for stock FreeBSD
00:46:29 <jbo> have not looked back
00:47:01 <Nux> appreciate it, but I was just given it and told to do some task with it, not my choice
00:47:05 <Nux> anyway, thanks for the help
00:47:55 <jbo> cheers
01:00:49 <rwp> Nux, Really just using the background image of the icon background is good enough though, right? :-)
01:03:42 <Nux> rwp, you know, web dude :)
01:03:58 <Nux> *you know it
01:04:19 <rwp> It was fun to find someone else who knew that reference.  It's a new classic!
01:04:38 <Nux> yeah, that's how I discover the over-40s
01:05:18 <rwp> Hold on...  I'll start reciting Holy Grail references... :-)
01:05:56 <ek> Shrubbery!
01:06:08 <ek> ... and, back on track.
01:06:18 <Nux> those will have to wait for tomorrow, it's 2am here, night folks
01:06:24 <rwp> In Japan it's the knights who say 2.
01:06:36 <rwp> Good night!
01:07:29 <rwp> scoobybejesus, I never knew about that cron_flags -J 60 option.  And the -j 60 too.  That's pretty useful to avoid the thundering herd problem.
03:37:48 <deepthaw> what would be the best way to setup x without a video card? still want to be able to connect remotely.
03:38:14 <nmz> VNC+
03:38:17 <nmz> VNC?
03:38:36 <nmz> remote X is S L O W
03:40:11 <rwp> deepthaw, You said two things that in my world are in conflict.  "remotely" and "x".  Those do not go together.  Remote X is so painful with any of the technologies that I suggest not using it.
03:41:26 <rwp> What things do you want to be doing with this remote system?
03:42:32 <nmz> I use my pi via VNC, its fantastic
03:42:56 <deepthaw> well phooey then.
03:42:59 <rwp> How remotely is your pi?  Across the LAN is not remote.  That's Local Area Network.
03:43:33 <nmz> I mean, remote X via LAN is still terrible
03:43:36 <rwp> deepthaw, You can still try it.  I may poo poo it but people do things I don't approve of all of the time! :-)
03:43:56 <nmz> meanwhile, VNC is good
03:44:13 <rwp> VNC is much better than raw X for certain.
03:44:19 <nmz> but you're right, however, I'm not going to open the ports
03:44:35 <nmz> but I'm sure its doable
03:44:48 <nmz> you can always use arcan
03:45:25 <nmz> and by use I mean, become a developer because only devs can use it
03:48:33 <rwp> I don't know if the linux compatibility layer would allow NoMachine to work but it's better than VNC.
11:45:12 <agni> hi folks
11:45:19 <agni> I'm new to BSD
11:45:41 <agni> and the journalctl follow log option does not work I think
11:46:10 <agni> it gives me a non-zero exit code
11:46:29 <agni> I have read in the UNIX handbook it's not good
11:49:31 <jan0sch> journalctl is a systemd/linux thing, here you want something like `tail -f path/to/your/logfile`
13:05:27 <jimmiejaz> I think my HDD is dying ahcich0: Timeout on slot 13 port 0   (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 0    (ada0:ahcich0:0:0:0): CAM status: Command timeout
13:31:44 <VVD> jimmiejaz, or cable
14:20:12 <Soni> can you compile freebsd on a pi4 8gb
14:24:05 <Soni> (as opposed to using a memory-constrained VM with no disk space)
14:52:48 <regis> I compiled FreeBSD on raspi1 from 2011 (which serves me well since 2012 to date). It takes time but worked.
14:53:20 <regis> I wouldn't try to "compile" FreeBSD documentation to HTML with Hugo or Jekyll though ;)
14:58:23 <Soni> so long as we can use -j4...
14:58:34 <Soni> is 8gb enough for -j4?
15:38:38 <kevans> Soni: ~1.5-2gb budget per job seems fairly reasonable to me
16:12:09 <tjpcc> I'm having trouble starting a vnet jail
16:12:11 <complexnumber> hello... C neophyte here... Am starting to read /usr/src... Any tips on where to start? I'm guessing start with userland..
16:13:00 <tjpcc> I'm trying to pass it an epair (the "b" part) and it looks like it performs "ifconifg epair0b vnet 0" but that command is failing with "SIOCSIFVNET: Device not configured"
16:13:49 <tjpcc> I'm trying to do all the ifconfig setup in "exec.prestart += ..." and I'm probably just missing something
16:14:20 <tjpcc> but i create the interface and run an "ifconfig epair0b up", and...I'm not sure what else should be required
16:15:47 <tjpcc> https://pastebin.com/rnCpUxPW
16:18:00 <kevans> tjpcc: vnet 0 seems wrong
16:18:43 <kevans> vnet 0 is the first vnet for prison0 ("the host"), a jail with a new vnet will (iirc) be assigned vnet# that matches the new jail's jid
16:19:06 <tjpcc> oh that's probably my problem - I tried counting from 0 and I was explicitly setting "jid = 0"
16:20:46 <tjpcc> kevans: thank you! using 1 works fine
16:28:46 <kevans> tjpcc: ah, good to hear. sorry that the error message sucks / leaves so much to be desired
16:29:45 <polarian> Hm... if you have multiple networks in wpa_supplicant, your device will continuously broadcast until one of the APs is picked up? But this means other people around you can intercept what SSIDs your device is looking for, no?
16:30:00 <polarian> the only way to fix this is to comment out SSIDs you do not want to connect to in public...?
16:30:08 <polarian> and then reload wpa_supplicant
16:30:17 <polarian> or is there a better way to do this?
16:32:12 <tjpcc> is "exec.poststop" a reasonable place to put "ifconfig epairXb destroy" to clean up the epair? "service jail stop" is bringing down the jail just fine but I'm finding the epair is still there.
16:33:50 <tjpcc> from testing I've found I can call destroy on either the a or b, so I've got: exec.poststop = "ifconfig ${vnet.interface} destroy";
16:36:02 <tjpcc> ah sorry I figured this out pretty quick. I think the poststop runs too early and the 'b' was still hidden on the host. It can destroy the "a" side just fine though.
16:39:32 <complexnumber> all good. just found the FreeBSD Developer's Handbook and Architecture Handbook.
16:41:15 <kevans> polarian: if you ktrace your bhyve start, anything interesting in subsequent kdump for nmdm?
16:44:57 <rwp> tjpcc, Here is some copy-pasting out of a working jail example here (which uses a second NIC for jail networking): https://paste.debian.net/plain/1323452
16:45:08 <polarian> kevans: never used ktrace before... not too sure how to do this...
16:45:21 <kevans> ktrace -di bhyve ...
16:45:31 <kevans> then kdump | less and poke through it
16:45:31 <polarian> thanks :)
16:45:45 <polarian> I missed the d
16:46:26 <polarian> ktrace: unknown facility in bhyve
16:46:28 <polarian> hm
16:47:21 <polarian> wait
16:47:45 <kevans> shouldn't see that unless you passed 'bhyve' as an argument to -t for some reason
16:48:13 <kevans> ktrace -di <command you were already using> should just work
16:48:19 <polarian> thats what I did...
16:48:57 <polarian> wait hold on... I think I typoed
16:49:12 <tjpcc> rwp: thanks, its helpful to see examples
16:49:25 <polarian> yeah apologies I typo'd it :)
16:50:27 <rwp> tjpcc, That's from a "lab machine" I am using to try things out myself.  I am using the second NIC connected to bridge0 for all of the jail networking.  That's going to need to be somewhat different on a single NIC system.
16:51:03 <rwp> I don't (yet) do anything with IPv6 there, because I don't have IPv6 here on this network to do anything with.
16:51:47 <tjpcc> I mean for networking just between jails there's no NIC needed at all
16:51:54 <polarian> kevans: kevans I got the ktrace... although I am not sure what I am looking for to be honest...
16:52:18 <kevans> polarian: maybe let's just start with: `kdump -H | grep nmdm | nc termbin.com 9999`
16:52:29 <kevans> if there's anything nmdm-related in that bad boy, we can dig deeper
16:52:40 <polarian> oh I used the wrong flag
16:52:45 <polarian> that would explain the useless data :P
16:52:49 <rwp> tjpcc, Here is the jail gateway2 pf.conf file to do the "virtual lab" internal routing: root@zima2:~# cat /jails/gateway2/etc/pf.conf
16:52:55 <rwp> ext_if = "ja0"
16:53:00 <rwp> int_if = "ja1"
16:53:05 <rwp> #table <rfc1918> const { 192.168.0.0/16, 172.16.0.0/12, 10.0.0.0/8 }
16:53:10 <rwp>  
16:53:15 <rwp> # Allow anything on loopback
16:53:20 <rwp> set skip on lo0
16:53:25 <rwp>  
16:53:30 <rwp> # Scrub all incoming traffic
16:53:35 <rwp> scrub in
16:53:40 <rwp> ##no nat on $ext_if from $int_if:network to <rfc1918>
16:53:45 <rwp> no nat on $ext_if from $int_if:network to 10.0.0.0/8
16:53:50 <rwp>  
16:53:55 <rwp> # NAT outgoing traffic
16:54:00 <rwp> nat on $ext_if inet from $int_if:network to any -> ($ext_if:0)
16:54:05 <rwp>  
16:54:10 <rwp> # Reject anything with spoofed addresses
16:54:15 <rwp> antispoof quick for { $int_if, lo0 } inet
16:54:20 <rwp>  
16:54:25 <rwp> # Default to blocking incoming traffic, but allowing outgoing traffic
16:54:30 <rwp> block all
16:54:35 <rwp> pass out all
16:54:40 <rwp>  
16:54:45 <rwp> # Allow LAN to access the rest of the world
16:54:50 <rwp> pass in on $int_if from any to any
16:54:55 <rwp> block in on $int_if from any to self
16:55:00 <rwp>  
16:55:01 <polarian> kevans: https://termbin.com/24hj
16:55:05 <rwp> # Allow LAN to ping us
16:55:06 <polarian> one line :P
16:55:10 <rwp> pass in on $int_if inet proto icmp to self icmp-type echoreq
16:55:15 <rwp>  
16:55:19 <kevans> polarian: also, can you describe your setup a little bit more? are you running bhyve(8) on bare metal just on the host, or in a jail, or something that needed back flips?
16:55:20 <rwp> Oops!  That was supposed to be https://paste.debian.net/plain/1323453!!!
16:55:25 <rwp> I am surprised the global bot did not kick me for that.  Sigh.  Oh well.
16:55:28 <polarian> kevans: bare metal
16:55:30 <rwp> After that goof I think I will crawl back under my rock again.  Sorry everyone!
16:55:31 <polarian> rwp: please use a pastebin
16:55:35 <kevans> polarian: w/o jail?
16:55:39 <polarian> yes
16:55:41 <polarian> sorry...
16:56:06 <polarian> does the handbook have information on ktrace + kdump?
16:56:18 <polarian> there is a section on kernel debugging but a brief search I couldn't find ktrace mentioned
16:56:21 <kevans> polarian: ok, so we'll need some more context there- can you just drop the full kdump into a termbin, please?
16:56:25 <kevans> not sure
16:56:53 <polarian> kevans: https://termbin.com/atkp
16:57:34 <kevans> seems to be truncated, didn't realize there was a limit
16:58:05 <kevans> I guess maybe the last grep you posted to termbin, but add something like -C 20
16:58:15 <kevans> 20 lines of grep context should be fine
16:58:25 <polarian> sure
16:59:17 <polarian> kevans: https://termbin.com/b44u
16:59:47 <kevans> ok, so there's something else going on, maybe
17:00:00 <kevans> we opened nmdm0B just fine, which means the clone worked and nmdm(4) likely absolved of guilt
17:02:43 <polarian> kevans: so... what do you advice then :)
17:05:47 <polarian> advise*
17:07:21 <kevans> hmm
17:09:03 <kevans> so we have nmdm allegedly wired up to com1, but neither side is showing up in /dev
17:09:25 <polarian> Indeed.
17:09:41 <kevans> -40
17:09:42 <polarian> works just fine when i tried with cu... opened a nmdm device (A) and then A and B showed up just fine on the host...
17:10:03 <kevans> (ignore that math bit, sorry, something else)
17:10:05 <kevans> hmm
17:12:25 <kevans> I think that'd suggest we closed the nmdm for some reason
17:15:40 <polarian> wait let me try with stdio then
17:16:36 <polarian> hm actually
17:17:01 <polarian> kevans: https://dpaste.org/02nPU
17:17:07 <polarian> then sh: turning off NDELAY mode
17:17:50 <polarian> detaches from standard output too?
17:21:14 <kevans> I'ma fraid you've exhausted by bhyve knowledge several lines ago :-)
17:21:18 <kevans> s/by/my/
17:24:32 <polarian> still had more knowledge than me :P
17:25:02 <polarian> welp I guess I wait on the mailing list and hope some very smart developer can help out :P
17:33:11 <skered> What make freebsd-update second install (userland) so dog slow?
17:47:38 <beowuff> "sudo bastille pkg ALL upgrade -y"
17:47:41 <beowuff> I love FreeBSD.
18:27:26 <tjpcc> hmm my jail is stuck in the dying state
18:47:44 <tm512> so I guess I'm likely to return to FreeBSD as a server OS for the first time in several years. have had DragonflyBSD on my home server since around 2014
18:51:10 <thorre> welcome back
18:51:42 <tm512> HAMMER is nice especially since my old home server only has 2GB RAM, but unfortunately package updates are quite slow to come down the pipeline. there hasn't been a single update to the ports collection (and packages by extension) since february
18:55:57 <tm512> ports is automatically pulled from FreeBSD and combined with patches, but all of that happens in a staging branch which has to be manually merged before the repo builders pick it up
18:59:23 <tm512> as much as I like running more obscure OSes, I also like having up-to-date software, and the "obscure" part sorta entails that there's not a lot of manpower behind the (presumably very tedious) process of maintaining a repo
19:03:00 <tm512> was considering OpenBSD or NetBSD for this new box I picked up but I've got one application for it where I'd really like to have the ability to put a hard limit on the CPU % this application takes up, and it appears that FreeBSD can do that
19:06:39 <tm512> I run a chess bot on lichess. my current home server is like a 15W Atom, so I can let the chess engine drive the CPU at full tilt without wasting much power or generating much heat, but this new box has like 6x the TDP
19:07:20 <tm512> it seems like I can cap the CPU percentage that an entire jail is allowed to have, though I'm not sure if I can do it outside of a jail, just for a single process and its children
19:08:33 <tm512> if there's like a generic Bastille template I can build off of for a python application, then spinning it up in a jail might be convenient enough
19:22:38 <zwr> there's a program called cpulimit that sends SIGSTOP/SIGCONT to a process according to its CPU usage https://github.com/opsengine/cpulimit
19:44:30 <tm512> apparently there's rctl for resource limits though it seems like it requires a custom kernel build? at least as of 2015, so maybe that's too out of date https://forums.freebsd.org/threads/limit-cpu-usage-by-process.52556/
20:00:35 <kevans> tm512: it's standard in GENERIC these days
20:28:45 <nicholaus04_> Howdy, folks!
20:29:17 <nicholaus04_> Managed to get an extra PC(Free of charge from a friend of our family).
20:29:48 <nicholaus04_> And of course, managed to install FreeBSD on it.
20:29:57 <nicholaus04_> In fact, i'm using it right now.
20:30:56 <nicholaus04_> Which means, i now have 2 FreeBSD installs, 1 being a i3/486 Laptop, and the other being a x86-64/amd64 PC.
20:31:26 <Hecate> nicholaus04_: cheers mate
20:32:25 <nicholaus04_> And my brain just realized i'm already on libera.chat, but on another PC(My linux one.). Hence why i have an underscore after my name.
20:32:44 <nicholaus04_> Hecate: Also, thanks!
20:34:31 <nicholaus04_> Included with the same thing, was a few old phones (One android powered one, and a flip-phone.), and a monitor that was meant to be used on the new PC, that i decided to use for my current linux-based one. And a printer.
20:36:33 <zwr> I like to install a different OS on each when possible, I can use them for testing program on all
20:36:42 <zwr> s/program/programs/
20:36:59 <nicholaus04_> And yes, just like my current PC, it's an HP one, with 4 CPU cores. But unlike it, it doesn't have much in the way of RAM.
20:37:38 <nicholaus04_> Another thing is that it even has out-of-the-box support for PS/2 components in addition to USB.
20:37:53 <kevans> zwr: this is what VMs are for :-)
20:38:26 <nicholaus04_> kevans: True, but there are some cases where you need to test it on actual hardware.
20:38:46 <zwr> my main machine is OpenBSD which is terrible for VMs, and real hardware is different. I already found a bug in the NetBSD kernel just by trying to boot it on a machine, panicked on startup.
20:41:01 <kevans> i'd argue that the vast majority of people aren't testing things where the distinction between baremetal vs. virtualized is important
20:47:29 <zwr> you can find bugs specifically by running it in a kind of VM too. One time I wanted to learn 8086 assembly but discovered interrupt 1 was broken on DOSBox when I tried to DEBUG.EXE a program. The entire register file would randomly corrupt, but only rarely
20:48:30 <zwr> just do both I guess. But I wonder how many people are doing real hardware vs virtual machines?
20:49:14 <zwr> I haven't found anything specifically because of the hardware on my FreeBSD laptop, but I've compiled plenty on it. It's nice to have no load on my main machine
20:49:52 <zwr> the DOSBox thing was using the FreeBSD laptop too
20:49:52 <nicholaus04_> For me, i would just do both real hardware/bare metal, and VMs in terms of platform support tests.
20:50:54 <nicholaus04_> Though for (MS-)DOS, i would perfer doing real hardware tests first, then testing on DOSBox(-X).
21:06:37 <nicholau104> Howdy, folks!
21:28:50 <momken> Hello
21:29:25 <momken> I tried to install gitea in an iocage in TrueNAS Core which is based on FreeBSD
21:29:40 <momken> When I manually run gitea it works just fine
21:29:58 <momken> But when I try to 'service gitea start' it does nothing
21:30:34 <momken> The jail is based on 13.3-RELEASE
21:30:44 <momken> Can it be a bug of 13.3?
21:31:31 <scoobybejesus> i am running gitea in a jail.  it started as probably 13.0 and now is 14.1
21:33:01 <momken> scoobybejesus, I get nothing after 'service gitea start'
21:33:31 <scoobybejesus> i assume the rc script is there in /usr/local/etc/rc.d/ ?
21:34:06 <momken> hmmm
21:34:13 <momken> it is /usr/local/etc/rc.d/gitea
21:34:40 <momken> it is listed in output of 'service -le'
21:36:39 <momken> it is its content: https://paste.debian.net/1323494/
21:39:32 <scoobybejesus> i mean, one thing you could do, which will give a lot of output to sift through (ideally, the only interesting bits will be at the end when it presumably fails) is to edit the script and put a `-x` i think it is on the shebang line so it will print out everything it does
21:40:45 <scoobybejesus> interesting.  mine doesn't have the start_precmd
21:40:53 <scoobybejesus> maybe i should add it
21:41:21 <scoobybejesus> i also don't have the thing, it's checking on, the gitea_configcheck_enable variable
21:45:24 <momken> scoobybejesus, It does only 'gitea doctor check' before starting gitea
21:46:18 <momken> scoobybejesus, So you say the 1st line should be '#!/bin/sh -x' ??
21:46:37 <scoobybejesus> yeah, i would try that and see the output
21:50:23 <momken> scoobybejesus, Can you understand anything from the output? https://paste.debian.net/1323501/
21:51:49 <scoobybejesus> looking at the end, it looks like it launched.  what do you see if you tail the /var/log/daemon.log ?
21:52:54 <momken> scoobybejesus, I see this https://paste.debian.net/1323502/
22:00:31 <scoobybejesus> ah right
22:01:02 <scoobybejesus> sorry.  how about tail /var/log/gitea/gitea.log
22:04:33 <momken> https://paste.debian.net/1323503/
22:05:07 <momken> something is wrong when it wants to listen on port 3000
22:05:40 <scoobybejesus> PID 36652. Received SIGINT. Shutting down...    odd
22:06:14 <scoobybejesus> do you have something else running that is taking port 3000?  maybe the gitea you manually ran is still running?
22:06:42 <momken> scoobybejesus, How could I know that?
22:06:58 <scoobybejesus> ps aux | grep gitea
22:07:04 <scoobybejesus> or look in htop/top
22:07:58 <momken> yeah there is a process gitea already there
22:09:52 <scoobybejesus> the second column is the pid, i think.  i think you can kill -9 ###, where ### is the number of the pid
22:11:18 <scoobybejesus> or just restart the jail
22:11:44 <scoobybejesus> which would start the process on it's own
22:12:38 <momken> scoobybejesus, I think it only recognize 'grep gitea' https://paste.debian.net/1323504/
22:13:06 <momken> No gitea at all
22:13:42 <scoobybejesus> sockstat -l -4 | grep 3000
22:14:08 <momken> no output
22:14:45 <scoobybejesus> is this a vnet jail?
22:14:55 <momken> scoobybejesus, Of course
22:15:36 <scoobybejesus> the IP address you gave it is different from the host address, i assume?
22:16:04 <scoobybejesus> i was going to tell you to do the same sockstat command on the host, but i guess the host should not be an issue
22:17:42 <scoobybejesus> in your /usr/local/etc/gitea/conf/app.ini, in the [log] section, is there a LEVEL listed?  mine is at Info now.  maybe you should try again with LEVEL = DEBUG or even TRACE, and then running again and looking at the log output again
22:25:52 <momken> scoobybejesus, It always gets these 2 lines in gitea.log:
22:25:54 <momken> 2024/07/17 00:15:35 ...s/graceful/server.go:70:NewServer() [I] Starting new Web server: tcp:192.168.8.204:3000 on PID: 36652
22:25:54 <momken> 2024/07/17 00:15:45 ...eful/manager_unix.go:203:handleSignals() [W] PID 36652. Received SIGINT. Shutting down...
22:26:59 <scoobybejesus> I can't remember if vnet jails need this enabled, but in your jail.conf, you might want/need allow.raw_sockets = "1";
22:27:32 <scoobybejesus> but i am running out of ideas
22:43:21 <momken> scoobybejesus, Maybe it's a bug: https://github.com/go-gitea/gitea/issues/25159
22:44:57 <scoobybejesus> i'm on 1.21.6 fwiw
22:45:31 <momken> my gitea version is 1.21.11_3
22:45:54 <scoobybejesus> also, that doesn't look like a bug.  the person wrote a script that misbehaved
22:49:11 <scoobybejesus> a curiosity i have is if you changed -p {pidfile} to -P {pidfile} (capital P) and commented out the procname line
22:54:21 <momken> hi
22:54:44 <momken> aaaaah
22:55:08 <momken> file /var/run/gitea.pid is always empty
23:08:26 <javashin> hi , on linux there is a xbox one controller driver called xone which let me use the controller as usb audio card and works nicely on one pc i have without integrated sound card i was able to make the xobox controller here on fbsd with xbox360gp driver but no sound working anyone have an idea how to make it work ?
23:57:13 <scoobybejesus> anyway, momken, this is what i followed when i set it up: https://www.ccammack.com/posts/jail-gitea-in-freebsd/  .. not much to it, though it seems like you have something else going on.  i don't know how to find where that SIGINT came from