is there a winamp like that works in bsd ?

used to use XMMS2 but i think thats deprecated ?

and whats the correct way to restart audio related services ?

hernan604: Use audio/audacity to replace xmms.

Not sure what you mean by restarting audio-related services. If it's a service, it should be restart-able by the "service" command.

ek: my problem is, i use an external amp via USB. So i have to set sysctl hw.snd.default_unit=2 to use it. It works fine for some 30 days +- or more, but then audio output starts to crackle a bit... im not sure why. i have reseted the amp, restarted devd, but the crackling continues

so im not sure how to reset the complete audio stack

(maybe this can help)

(maybe reseting the complete audio stack can help it get to the initial state and no crackling... or, i will need to reboot.. but i dont want to)

hernan604: Hrm. I've never had the problem before. If you do reboot, it fixes the problem?

ek: if i reboot, yes it fixes the crackling

this is a long going issue with this external usb amp. after some 30, 50 days of uptime, it starts crackling. and the problem is not the amp.

its somewhere in freebsd

but im not sure where... or what services to restart to attempt a fix

hence why i would like to restart the "audio" related services

but im not sure what those are neither

running 14.2-RELEASE

hernan604: What audio services are you running?

ek: how can i check ?

i dont think its anything outside the usual

but let me know if you have some command i can use to check that

but it should be just the ususal.. from a fresh install... and manually setting sysctl hw.snd.default_unit=2

to get output for the amp

there must be a solution :)

maybe reboot yes.. but i dont want that

maybe its because i have youtube opened and mocp

but im not sure

hernan604: searching for winamp in the long descriptions of ports yields qmmp, sayonara and d11amp, I haven't looked further at them, but maybe one of them is what you search

Good News Friends, I have successfully install FreeBSD

now I just need to incorporate the technologies I need for my work

I think an /etc/periodic.conf.d/ would be a welcomed addition.

Each app you have could install it's own file (e.g. /etc/periodic.conf.d/pf_droplasso) - this seems very easy to script for automated configuration tools.

dvl: isn't that what /usr/local/etc/periodic is for? e.g. dehydrated installs /usr/local/etc/periodic/daily/000.dehydrated

or do you mean for per-service conf files

ivy: Yes per-service configuration files

"The periodic.conf file is actually sourced as a shell script" so you could add a ´for conf in /etc/periodic.conf.d/*.conf; do source "$conf"; done´ and maybe it would be good for the default, but I don't think ports themself should install a config there, for configuration management tools I can see the use case

i'm thinking of submitting a patch to add a new rc.conf option: ifconfig_xxx_wg="/some/path/to/wg.conf", which would just run "wg setconf $interface $file" when the interface comes up. any opinions? i'd personally like this as it saves creating a bunch of one-line /etc/start_if.* scripts

Seems as if it'd be worth submitting. I don't use wireguard so I'm not all that qualified to say, but it seems as if it'd be helpful and the worst that happens is it's rejected, no?

ivy: how about the wireguard service from wireguard-tools@lite ?

nimaje: as we have wg(8) in base it seems silly to install a port just to get an rc script

of course, people could still do that if they wanted

well, that service could be imported into base instead, especially as it only lives in the ports tree

nimaje: oh thanks

I have incorporated xfce desktop on top of FreeBSD14.2, but I noticed, if I try to change the wallpaper, it wont change hehhee

hmm, I was looking into implementing brace expansions in /bin/sh but it's not straightforward to make them work when nested

I'd hate to add 1000 lines of code just for this