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?