well, you can propose the patches upstream already, upstream and the port don't need to way on one another there, in the port you want to make the current release build on freebsd and upstream you want to ensure that the next version builds on freebsd, there are no dependencies between those two goals

The multitail program in FreeBSD has a memory leak. If I leave it running it eventually absorbs gigs. It doesn't have this leak on GNU/Linux systems. I guess I should debug it at some point.

Bugzilla time!

I am embarrassed to say I simply rebooted the system a few times before chasing down that it was my multitail run in a terminal that was the program eating up gigs of ram, which forced a growing swap usage.

And now it is pretty easy to 'q' and then C-p Enter (one could !! it) to restart it so that's what I have been doing since I figured it out to this program.

rwp: The terminal is running away with mem? Terminal emulator?

XTerm is okay. It's multitail.

Oh, I see. Still the same problem existing, you're just saying it took some time to figure out it was, in fact, multitail causing it.

Right. Check out how much swap it consumes when it is deep into the leak: proulx.com/tmp/multitail-memory-leak.png

what's wrong with `tail -f *`? that doesn't leak

multitail runs tail -F across multiple files and displays all of the files in one terminal window, optionally merging output of multiple files.

Unfortunately for me there are cohorts who have created literally tens of apache *access.log files and I can use multitail --merge-all *access.log to merge them all in one window to look visually for abuse patterns. That's a useful feature. And can look at multiple other files for abuse such as multitail auth.log fail2ban.log messages to view multiple logs in different curses windows.

And I suggest looking at the difference between tail -f and tail -F. I am bummed that the behavior of -F didn't make it into -f as it ought to have done. But that's spilled milk under the bridge decades ago now. Always use -F instead of -f if there is any possibility that the log file will be rotated.

how to fix it?

# jexec a xfe

FXApp::openDisplay: unable to open display localhost:10.0

Chip1972, You appear to be trying to run a GUI application inside of a jail without connecting that up with the desktop outside the jail.

Chip1972: what is your goal

i want to learn

xfe is a gui file manager. Probably not a good choice to be trying to use in a jail. ls is probably a better choice for use into jails.

what?

jail != jails ?

I see the "jexec" followed by "a" and I think you are trying to execute a program in the jail named "a". And the command I think you are trying to run is xfe a graphical file manager.

if you want to learn then either try it without a jail or read up on the x protocol to learn why it's not working

But if you are just learning then attaching the graphics from a jail to the hosting desktop is rather involved. There are lots of articles on how to do this on the net. I quoted one earlier today.

Better while learning to stick to the simple command line in a text terminal. That's the best way to learn.

I am scrooled

ivy: hey what's up?

can you give me some info regarding the process of contributing to the freebsd source?

no I mean how does the hiearchy thing works?

like who gets to be the commiter and maintainer this and that?

"maintainers" only really exist in ports, anyone can become a ports maintainer by submitting a new port or taking over an existing unmaintained port. commit access (to either src or ports) is usually given to people who have a history of submitting useful changes

ivy: okay who gets to decide if someone is a commiter? and are you one?

there are mentors and mentees

the book i am reading tells me to find a commiter to talk to before trying to contribute

anyone can propose someone for commit access, it's decided by a vote (of core, i think... or is it srcmgr? one or the other). i am a committer, yes. but... being a committer doesn't really mean anything, it just makes it a bit easier to get your changes into the code

okay alright

what is a "port"? is it part of the system image shipped online?

they're third-party packages, i.e firefox

okay alright

thx for the tips

do you guys have a conference like debcon every year, where people show off the latest cool stuff?

yes, bsdcon etc.

freebsd.org lists some of the events

okay alright

rwp: interesting, I am the packager for multitail. I'm actively using it in two separate virtual TTYs with screen with tailing logs and tailing script execution output, haven't noticed a high memory consumption — although I have 64GB ram on the server so didn't have to watch for any OOM. if you can reproduce it somehow (maybe feeding huge amounts of logs and seeing if RES raises significantly), we

could get a hint of what happens. that said, the packaged git tag is quite old and there have been a couple changes added into master ever since: github.com/folkertvanheusden/multit…8bed410f1bbf86f247c059546d9..master

zi: why does net/fiche create a user when the service doesn't use it and runs as root? did you just forgot : ${fiche_user:=fiche} in the service?

hm, the pidfile has to be created before too, so that daemon can write it, but seems to work fine like that

pkgbase-based upgrades are fast

basifying 14.3 and transitioning from 14.3 to 15.0 took only 20 minutes and one reboot

bleh, kinda hate when I find something I need and their only supported installation method is.... docker compose

I know FreeBSD has containerd & runj but haven't looked to see if there's any reasonable way to do something like docker-compose with this, or if I should just give up and run some minimal Linux inside bhyve

I see nerdctl supports this, but is also pretty early in terms of FreeBSD support, hmmm

well, if docker is the only supported installation method, then it hints at the installation being so convoluted and shitty that they wanted to sweep it under the carpet

well yes obviously but people get pissy when I tell them this

I've made the point repeatedly to people: having the *option* of Docker is great, when deploying and integrating software, or even just running software whose dependencies, required configuration, or privileges just badly overstep. Developing software under the assumption that it will be there is not.

hodapp: it will probably work at least under two different OSes, WSL is proven to support Docker images

so no worries, you can change OS, and if you want to really run it under FreeBSD controll, then wirtualise the OS hostion your app

hodapp what software is it? whatever it is, it has to run without Docker anyway :-))

I really wanna know :D just to add that software to my blacklist ahaahah

antranigv: immich

antranigv: someone's made derivations in NixOS for it, so it definitely *can* run without Docker, but I dunno what's involved

also: github.com/immich-app/immich/discussions/1657

mzar: my 14->15 pkg base upgrde went very very wrong

but i just yolod it

hodapp: `podman compose up -d`

after `kldload linux`

i don't know if immich would ru nit it

rtprio: it requires adding signatures from 15.0 and yes, I had to replace master.password and group with old verions

but the whole transition is seamless if you have root on ZFS and the ablility to create new BE

it was my first try to pkgbasify and do major version upgrade, and I am impressed <- Good Job PkgBase Maintainers !

I will script it and make transition of a bunch of workstations next month

even in the 14.1-14.3 the /etc/rc.d/ldconfig never properly merges

karolyi, Hi! Just replying that I see your messages to me. No immediate time but I will see what I can do to produce a reproducer for you in the near future. :-)

rwp: whenever you do reproduce a reproducer by reproducing the reproducable, please open a bug ang ping me there :)

*and

Feel free to break out into a Gilbert and Sullivan Pirates of Penzance song but I am not joining in! Last time I sang for my supper they called it extortion. :-)

Say, is the latest version of FreeBSD for armv6 raspberry pi 13.5-RELEASE because that's the newest version that'll build or is it because it's the newest version someone's bothered to build?

zip: armv6 is no longer supported

Nor is i386 :-(

i386 should be

I think 15.0-release might be broken right out of the box if you pick the pkgbase install option. I do see there is a bugzilla that seems to be actively commented on bugs.freebsd.org/bugzilla/show_bug.cgi?id=292214

15.0 aarch64 to be clear. Since that seems to make a difference.

i think i386 is dead in 15

Ah, so no point attempting a 14 build then

Once again I should obey the note I stuck on the damn thing that says "get a real computer to tinker with"

AmyMalik: could be true, but for 14 i386 is still supported

zip: armv7 is still among supported architectures

the first Pi is arm6 i believe

mzar, I believe I once golfed the i386 kernel down to be able to boot a VM in like 81 megs of ram

RPi2 is v7-based

the bootloader prevented me from going any further, I believe, had I used grub I might've been able to get it up and talking on 64

mzar, yes, the last version with i386 is 14.

OK

Yeah. I should put the zero in the bin

It was shit when it was new and that was over a decade ago

I just hate wasting old hardware and buying new hardware but I guess the solution to that is to cycle out the pi 4 from its home assistant duties and then tinker on that

I think it's pretty neat there's computers so light and low power that you could use one as a computation sidecar to your phone or iPad if you needed to

zip, or use a diffent flavour of BSD, and even Void Linux?

But realistically I also solved that problem in 2019 when I didn't have a computer for a while with a cloud-init script and a couple shortcuts and would boot up a VM for a penny an hour if I needed Python

i wonder if i have or could develop the skills to re-port FreeBSD to the 686 (I believe the i386 port was for 686 and up), solely as a one-off entertainment vehicle

?!

hi!, anyone using zelta for zfs backups here?. I'm using it since a couple of months now and it works great. Now I'm looking for a way to delete old snapshots, I don't know if Zelta has a built-in feature for this.

AmyMalik: FreeBSD was running fine on 486, without issues IIRC

ah

doesn't netbsd still support many of the older archs?

i believe so

I ran it on an a2000 amiga with a 120 GVP scsi hd years and years ago

have never tried it on an intel based system

did not really do much with it except conclude it worked fine

I had a 68040 card in I think

not particularly fast