Do people on FreeBSD usually use "multiwatch" to manage fcgiwrap processes? That's rather the standard in my world on the other side with linux systems.

I can install multiwatch from pkg ports okay no problem. But... There is no rc script for multiwatch. There is an rc script for spawn-fcgi which is usually used with it. And also an rc script for fcgiwrap itself.

For those that do this is the usual thing to do to configure the spawn-fcgi rc scripts for multiwatch? Seems plausible. Thought I would see what other people do about fcgiwrap processes in a high rate production environment.

What did the port maintainer(s) say about it?

Where would they say this? "pkg info -D multiwatch" has nothing said there.

rwp: Could send them an e-mail asking about the missing startup script.

based on the spawn-fcgi rc script and the multiwatch repo's README.md, it seems like the intention is probably to use the multiwatch binary as spawn_fcgi_app and spawn_fcgi_app_args as appropriate

the pkg descriptin for multiwatch does note that it's intended to be used with spawn-fcgi specifically

I am reading through that and I think it is something like that too.

Though I said spawn-fcgi on linux previously I should have said that on linux it is the fcgiwrap rc script which is usually configured for multiwatch. And I think actually that either the FreeBSD fcgiwrap or the spawn-fcgi rc script could be configured for this.

right, so the expected use is probably teh same, it's just not really explicitly documented as such

I know the result I want. Just trying to figure out what needs to be done to achieve that result. And strangely searching the web I don't see any blogs or articles from anyone talking about how this is done for them. That's unusual. Thought I would discuss here.

After I get it going I will endeavor to post a wiki article on how I set it up for this. (shrug)

2243/20

bah sorry

Hi

I am back agian

Some problem in my client.. fixed it

if I switched one PC from AMD to Nvidia, what do I replace kld_list="amdgpu" with?

darwin: Install nvidia drivers first

ok

i've seen a lot of those. It has GeForce RTX 4090 soon 5090

if I use Bhyve to run Slackware or something, which has drivers for my multi-function hub / media dashboard with alcor micro corp chips, could I then access memory cards, etc., in that in X in FreeBSD?

darwin: I only want you to not face my problem :(

are you from dev of Slackware

not officially

do you have knowledge in freebsd

I have a big problem :(

darwin: you're asking to first passthrough an unknown device to a VM, have that VM recognize it and make it usable, and then having your *host* access that device *via* the VM?

That sounds... convoluted, if possible at all

Alver: could you help me please..

if I can pass through all USB, then maybe

Retrofan: don't ask to ask, just ask

I already asked yesterday

it's a problem happend when upgrading freebsd

it removed the amdgpu

but it's still listed in rc.conf

and blacklisted in loader.conf

To fix that old bug

darwin: then you still won't be able to get to it from the host, I fear.

but now it crashes the screen; bec it can't find the driver

can write blindly, renamed rc.conf to rc.conf.old, but no luck

then reinstall it or the new version

tried unload modules from "OK prombat" and booting with "boot /boot/kernel/kernel" + -s for single user mode, but still no luck

pkg search amdgpu

No pkgs will work anyway

bec. the pkg upgrade install 13.5 pkgs

but the system is still on 13.2 base

i don't think you need the Linux kernel for amdgpu... I just had kld_load="amdgpu"; for Nvidia it starts kld_load="linux nvidia..."

Can you ssh into the box if the screen is not working ?

no ssh will work

then pkg update; pkg upgrade

no pkgs will ever work

fix pkg first

actually that won't work

sounds like messed up

why would you be installing from 13.5 without upgrading to that

darwin: there no problem in pkgs, freebsd-update install will work

that normal

upgrade command installs the laetest versions of pkgs

then you reboot

and run freebsd-upadte install

3 times

and it will work

but I can't see

the screen, then how do I know if there is problem happend?

I need to forvstop

yeah, SSH in and I suggest get OS/pkg versions matching before you start on graphics card

*force stop the system from loading those modules

darwin: no pkgs will work

only working in rescue

and freebsd-update install

My problem is not fixing the module

the command line can be reached without amdgpu

but the system is loading non-exits module, which crash it..

then don't load it until after fixing

but it still been loaded, even after unload

I've trouble understanding what is going on.. Can you reach a command line on the system or not?

I need to know what is in loader.conf

Hi divlamir

can reach but in crashed screen

write blindly

If it's a gpu driver issue, you should be still able to SSH in the box

I succesfuly reached anthor pc but the innternet connection here is lower than 500kb/s

divlamir: do you remember my problem

all pkgs is in 13.5 version

so no ssh will work with old libc and base

need to freebsd-update install

ssh is part of base

how?

Is there is bultin one!

builtin

well, yeah, it's not a package

ah, my bad

I remember that I can read loader.conf in the OK prombat

*promat

*p

you can just do 'unload' at the prompt

or choose load defaults from the menu

done that before

I think there someting other in that file

you can try booting kernel.old

flatdog: bat english XD

backups ?

backups of loader

?

Or, get mfsBSD and boot from a stick: mfsbsd.vx.sk

divlamir: what does mfs stand for?

memory filesystem right?

guys

loader.conf not found

look like it was deleted all that time

should I move backup loader.conf to /etc ?

"/etc" is on same partition of "/home"

Oof. Bad planning

Tenkawa: okay

but that's the difference between that and liveOS?

Has anyone got experience with (creating and) destroying tun devices programatically from C?

Alver: I had very slight such experiences

and I think in the official library source code pack there are a few usage examples

scottpedia: Creating a tun succeeds. But if I want to get rid of the device, that seems to be more tricky due to unknown open file descriptors and no apparent way to get rid of them. If I don't, SIOCIFDESTROY will hang in an uninterruptable state in kernel.

have far have you got?

If I only call close() on the fd, the device will be "disconnected" and unconfigured but nevertheless still present and visible in ifconfig.

scottpedia: well, I already managed to have to reboot three times so far because of this ioctl hang. I would prefer to avoid more of those. :°)

(it's a jail server, and it's everytime a bunch of services that have to come back up)

have you tried using ifconfig to destroy interfaces?

From C? No, I haven't. If there are open file descriptors - which is the prime suspect afaik - then ifconfig would also hang since it calls the same ioctls effectively

If my C code to remove the tun hangs, and I try to do remove that same tun via ifconfig in a terminal, then ifconfig also hangs

I suppose I could try to query procstat for all open fds, and loop over them to see who else has an open one on my tun, but that sounds super cumbersome

haha

Fixed!

I was just disabled hw.syscons in loader.conf

so after hw.syscons.disable=0 it worked!

now I am on single user mode!

Anyone else seeing this? ld-elf.so.1: /usr/local/lib/libidn.so.12: version LIBIDN_1.0 required by /usr/local/bin/lynx not defined (lynx installed via official pkg. Rebuild from ports fixed it. 14.3-R.

Unterminated parenthesis for attention

Now..

there is some problems with internet

look like freebsd-update fetch messed it up

my internet is 56k now XD

I am running freebsd-update install

literally, or?

but there is somethin wrong here

it's say is that I am using ZFS now

but I never used it before

Does the freebsd-update installs it automatically

Retrofan: what does `zfs list` show? your filesystem isn't automagically converted, whatever you started with, will still be the same after upgrade

but freebsd-update *might* load the kernel module to determine if you're using zfs or not.

as it will create a boot environment (a snapshot) if you have zfs, to make rollback easy

yeah I understood

upgrade successed

\o/ awesome

uname -r

prints freebsd 13.5

but..

alot of problems here :(

loader needs to be updates

and packges need to reinstalled

*updated

and NO internet

thats normal. updating base system is part 1, updating packages is part 2 after reboot

but not having internet is very awkward

maybe upgrade messed up hosts

and it says now my backup partition is not clean

run fsck

did you do `shutdown -r now` or use something else? otherwise it should be clean

ah

yesterday I unpluged the power cable

three times

this is why we use zfs where we can ;-)

why?

is it damged

?

if fixed the main freebsd ufs

and others

but that one is already embty

so no problem

formating it

dch: is zfs safe me from that?

yes

it has a number of useful features:

- copy-on-write. so even if you lose power, there is no fsck needed, so its always consistent

- inbuilt checksums, so you can catch errors and recover from them, instead of finding out only when the data appears corrupted later

so is it damged?

- lots of conveniences like boot environments, snapshots, easy replication

but it's eats ram :(

*it

for your ufs partition, you need to run fsck, yes

I run zfs on 0.5GB systems, it can be tuned not to do this

fsck didn't fix anything on that embty partition

but it depends on use case and needs, ufs is very reliable

dch: O_o

my pc is 8gb

I was all time thinking that it's a High-end workstation XD

good

I will try it later after I learn more

zfs is 20+ years old, back end 1GB was a very powerful system I guess

yeah, no need to rush into it

bec. there some strange stuff goes on my old mbr harddisk

it's not corrupted, but when I add any file to them..

it disappers next time I boot up

that sounds .. very bad

I read that a problem in freebsd

bec. I attached it to another Windows pc, and it's working well

well there you go then

but I need to fix that, I am not a WIN user ;)

more than 6 years

never touched any WIN on real hardware

I also want to learn about jails in freebsd

I head it's very useful for security

especially that I am using ports from earily 2000s

I will use zfs for my next freebsd 14 upgrade

when support end on 13.5

Please anyone kick my old nick; bec it changed du to internet connection

*due

ah bad luck agian.. the rc.conf is deleted for no reason, and backup of it is on the corrupted partition :(

so no internet

this sounds like very flakey hardware

yeah

ZFS snapshots FTW!

ah

finally fixed the backup partition, and copied the old rc.conf

and internet + multi-user mode is working :)

very happy to see freebsd13.5 when I log in :)

But.. my connection is 32k

super slow for anything

Now I need to fix my internet to speed it up...

err.. I really need to fix it

Anybody here use gnome with FreeBSD?

which version..

Don't tell me you've got Gnome 2 running..

I got gnome 1 to run before XD

I really like old gnome

and ROX

Glad you got your box back running Retrofan

if only lmao

It sounds a bit like a house of cards, bit he seems to be able to keep it up somehow :))

Wow. ROX. Haven't seen that in a while...

yeah rox and it's desktop stuff is the best!

divlamir: My box is running, but no internet for upgrading other packages, so it's still fully working

divlamir: yeah, my goal is to make stable as far as could :)

*it

I really want to share a screenshot here when I fully fix it

using Wmaker+rox desktop and some other stuff for my x11

So I seem to remember wmaker on fbsd had a grayish backround with "leeter than you" on it. Anyone remember anything like that?

This was about 20 years ago.

I was using afterstep

but it's not updated, and tons of bug

loved it's desgin but I can't use it :(

Time to go

Bye!

I am ashamed to say it but last time I used *any* desktop (read window manager) on FreeBSD was like 20 years ago, sigh..

Do you still use a gui?

Sure, from my linux laptop ssh-ed in my FreeBSD box :)

It's been the year of the linux desktop for 20+ years for me :P

yeah, I'm there with you honestly

Sorry. I was thinking a newer version.

I guess it sounds like gnome will be more dependent on systemd

But I was wondering what version fbsd has in the repos. I guess there is always mate to go vintage.

Almost sounds like I’d have better luck with plasma/kde if I want a ui for FreeBSD but I haven’t looked at it too hard since it takes quite a bit to get it going with Wayland.

I think ghostbsd is mate by default.

If I can actually manage to get the atheros wifi working in this thing I may give it a go with fbsd to see if I can do it. I just want to see if I could get a legit de going on an older A10 5800K

I have been running a FreeBSD desktop with a wired ethernet since 12.1. But I am a simple user of the desktop and don't stress things too much and don't need fancy things other than XTerms, Firefox, mpv, and sometimes LibreOffice. I can't remember when I last started anything graphical that was outside of that set of programs. Running i3 here also.

It's kind of incredible how little we actually need in terms of discrete products

rwp: ah. I know gnome can run on it quite well and that’s my go to when using Linux. I was just curious if the fbsd option was there.

I think the only issue I have with it is that the onboard wifi won’t work but I haven’t tried too hard either.

Macer, Up through 14.2 the WiFi performance on FreeBSD was measured in kbits per second and not megabits. Sad. The standard method was to use "wifibox" to have a bhyve linux kernel handling the wifi device. Amazingly that works quite well! In 14.3 a HUGE improvement to WiFi native performance. It's hugely better in 14.3.

But that caveat is why I mentioned that I am using a wired ethernet. That's high performance and no problems there at all.

As an i3 user I am not using Mate/GNOME2 but I thought it was working okay on FreeBSD. It's GNOME3 which was a complete burn-down-the-house rewrite which is now strongly requiring systemd. Avoid GNOME3. But Mate/GNOME2 is okay as far as I know.