00:11:08 <Beladona> RhodiumToad checking
00:11:16 <Beladona> whats the threashold?
00:11:17 <Beladona>  My drive activity starts and peaks "daily" runs at 3am and keeps running for hours. I read/ thought that was it.
00:12:02 <Beladona> RhodiumToad /etc/periodic.conf file does not exists
00:12:37 <V_PauAmma_V> By default, it's every 35 days, IIRC.
00:12:45 <RhodiumToad> then it's probably not zfs scrub that's your problem
00:12:48 <Beladona> V_PauAmma_V where?
00:12:50 <RhodiumToad> more likely it's the security run
00:13:02 <Beladona> RhodiumToad but on hdds?
00:13:22 <RhodiumToad> security run will do a find ... over every mounted local filesystem that's not marked 'nosuid'
00:13:40 <RhodiumToad> so if you have filesystems with very many files, that can take a long time
00:13:54 <RhodiumToad> ('nosuid' or 'noexec', I should say)
00:14:36 <RhodiumToad> you should set any filesystems that contain only data and not programs/jails/other executables to at least nosuid
00:14:53 <V_PauAmma_V> Beladona, "zpool status" will tell you when the last scrub took place.
00:14:57 <Beladona50> disconnected. I might have missed messages
00:15:04 <RhodiumToad> security run will do a find ... over every mounted local filesystem that's not marked 'nosuid'
00:15:07 <RhodiumToad> so if you have filesystems with very many files, that can take a long time
00:15:09 <RhodiumToad> you should set any filesystems that contain only data and not programs/jails/other executables to at least nosuid
00:19:13 <Beladona50> RhodiumToad ok how to set it nosuid
00:24:21 <Beladona50> like at the time of mounting?
00:25:48 <RhodiumToad> yes
00:25:56 <RhodiumToad> are you using zfs?
00:26:09 <Beladona50> yes
00:27:08 <RhodiumToad> you need to set the setuid=off property on the appropriate datasets
00:27:55 <Beladona50> RhodiumToad so its safe? I don't have exec files in that pool.
00:29:04 <RhodiumToad> why would it not be safe?
00:29:32 <Beladona50> # zfs get all big-drive |grep uid
00:29:32 <Beladona50> big-drive  setuid                on                     default
00:31:08 <Beladona50> doing zfs set setuid=off big-drive
00:32:30 <Beladona50> is it expected to take forever RhodiumToad
00:32:37 <Beladona50> maybe the hdd is busy
00:34:29 <RhodiumToad> I wouldn't expect it to take long, how long has it been?
00:34:56 <Beladona50> since 5 mins
00:35:23 <Beladona50> thanks, I will leave it to work.  should leave too myself
00:51:57 <Beladona50> RhodiumToad its done. thanks
01:34:27 <SpaceBass> Glad I'm not the only one with a zpool called big-drive
01:36:33 <bsdbandit> good evening everyone
02:06:31 <occ> Does freebsd support intel N100 CPU？
02:08:14 <occ> I'm not sure about whether freebsd support Intel N100(its NIC and display) or not.
02:08:40 <occ> there is not information about that in https://www.freebsd.org/releases/13.1R/hardware/
02:08:42 <VimDiesel> Title: FreeBSD 13.1-RELEASE Hardware Notes | The FreeBSD Project
02:08:49 <occ> s/not/no
02:09:52 <mason> no was correct in both cases
02:09:58 <mason> not* I mean
02:10:13 <mason> I guess either works.
02:10:56 <RhodiumToad> for the display, you'd have to look up the device id in the drm driver lists, probably
02:17:04 <RhodiumToad> and indeed, it's not in the list for drm-515-kmod
02:17:34 <RhodiumToad> so there's probably no better than framebuffer support for it
02:20:22 <occ> RhodiumToad:  it means I need waiting more time for the newer version of drm-kmod ...
02:20:43 <occ> RhodiumToad: mason: thank you.
02:21:20 <mason> occ: Might be worth asking in efnet/#freebsd-xorg
02:21:34 <mason> The big X brains are there.
02:22:22 <occ> mason: ok, thank you again.
03:25:55 <bsdbandit> so im running freebsd 13.2 and i wanted to changed the color of my boot up text so ive added the following lines to the new kernel options  SC_NORM_REV_ATTR=(FG_YELLOW|BG_GREEN)  options SC_NORM_ATTR=(FG_GREEN|BG_BLACK) options TERMINAL_NORM_ATTR=(FG_RED|BG_BLACK) and options TERMINAL_KERN_ATTR=(FG_RED|BG_BLACK) but when booting into the new kernel im still getting the default white text
03:26:08 <bsdbandit> not sure what else to try
03:30:36 <V_PauAmma_V> Did you check the options took with "sysctl kern.conftxt | grep -E 'options.*_NORM_'"?
03:32:03 <bsdbandit> ive used the sc options back in freebsd 12.x an it worked but looks like something has changed in 13.2
03:32:13 <bsdbandit> going to check that file right now V_PauAmma_V
03:34:08 <V_PauAmma_V> Also: sysctl kern.vty
03:34:31 <RhodiumToad> bsdbandit: man vt
03:37:09 <RhodiumToad> also, what hardware?
03:37:29 <bsdbandit> im running freebsd on thinkpad x1 extreme
03:41:56 <RhodiumToad> uefi boot?
03:42:04 <bsdbandit> yeah
03:42:09 <bsdbandit> running zfs as well
03:44:25 <RhodiumToad> anything in loader.conf ?
03:45:59 <bsdbandit> hey this is my load.conf https://bsd.to/zXKj
03:46:00 <VimDiesel> Title: dpaste/zXKj (Plain Text)
03:48:31 <RhodiumToad> most of those are probably pointless but should also be harmless
03:49:52 <bsdbandit> do i need to add something to the boot.loader.conf  ?
03:56:16 <RhodiumToad> shouldn't do.
03:58:28 <RhodiumToad> you checked you actually did boot the changed kernel and that it has those options in
03:58:37 <bsdbandit> yeah
03:58:50 <bsdbandit> FreeBSD banditbox 13.2-RELEASE-p2 FreeBSD 13.2-RELEASE-p2 GENERIC-BANDIT amd64
04:00:30 <kevans> I have a vague recollection that loader changes broke some of that
04:00:33 <kevans> one second
04:02:11 <bsdbandit> ok
04:04:11 <kevans> try setting teken.fg_color and teken.bg_color in loader.conf
04:04:30 <kevans> corresponding to the TC_* constants in /usr/include/teken/teken.h
04:05:01 <bsdbandit> ok would i need to recompile the kernel as well ?
04:05:12 <kevans> iirc loader will set them unconditionally now, so we don't fallback to TERMINAL_*_ATTR
04:05:15 <kevans> nah
04:05:22 <bsdbandit> ok
04:05:33 <kevans> tsoome_: ^ may remember the details on this a little better, I only very vaguely recall a report on it and don't remember if it got fixed
04:06:07 <kevans> i think it's only like 07:00 where he's at, though, so he probably won't be around for a while yet
04:13:23 <parv> Those "teken*" knobs are new to me. Setting the ones related to "*vt*" (for achieving the corresponding affect of setting colors via *sc* ) had been a futile effot.
04:13:42 <parv> s/effot/effort/
04:14:19 <bsdbandit> thank you all so much going to do some more reading in the morning need to head to bed
08:05:08 <andmars> morning, trying to install intel graphics and followed the handbook. So I did "pkg install drm-kmod" and "sysrc kld_list+=915kms" adding user to "video". I also created "20-intel.conf". Still I get the error "No drivers available". It works if I install "xf86-video-intel" which is not mentioned in the handbook. So which is the correct way to go here?
08:10:40 <parv> (Remove "xf86-video-intel" while using "drm-51*-kmod" ) Have you rebooted or loaded the "i915kms" kernel module?
08:12:32 <andmars> parv: yes, I have rebooted, still this error without xf86-video-intel
08:15:04 <meena> I think kmods are still built against 13.1, so you will have to build the port yourself
08:15:41 <parv> Do you actually have "915kms" in /etc/rc.conf, instead of "i915kms"?
08:16:25 <andmars> parv: I followed the handbook which states "sysrc kld_list+=i915kms"
08:17:50 <parv> I wanted to verify because earlier you wrote:  So I did "pkg install drm-kmod" and "sysrc kld_list+=915kms"...
08:18:46 <andmars> parv: typo on my part here in irssi...in rc.conf it's the correct line
08:19:32 <parv> andmars, Does the display flash as mentioned at after boot https://wiki.freebsd.org/Graphics#Intel_Integrated_Graphics_.28aka_HD_Graphics.29 ?
08:19:33 <VimDiesel> Title: Graphics - FreeBSD Wiki
08:20:02 <andmars> parv: yes, it goes blank for a second which it didn't do before installing the driver
08:22:56 <andmars> it also says "x11-drivers/xf86-video-intel is optional"
08:23:43 <andmars> "In most cases" that is...
08:23:46 <parv> andmars, As meena mentioned earlier, try with self compiled version of drm-*-kmod. You may need to declare some "Screen" device or set up "modesetting", I cannot say. Post the current "/var/log/Xorg.0.log" somewhere (for others to help)
08:56:09 <meena> we really need to do something about this. it's tripping so many people up
13:21:56 <debdrup> https://wiki.freebsd.org/DmitrySalychev/PinePhonePro might be worth keeping an eye on.
13:21:57 <VimDiesel> Title: DmitrySalychev/PinePhonePro - FreeBSD Wiki
14:17:32 <CmdLnKid> :q
14:17:40 <CmdLnKid> dumbit all
14:18:05 <CmdLnKid> active window is not allways the forground!
14:20:15 <Beladona>  dmesg: https://termbin.com/caxm  and now my file manager isn't working (thunar) . Not even opening. Is this nortmal in bsd/zfs
14:20:16 <Beladona> rsync stuck since hours, file manager not working, no file browsing . This happens sometimes.     766,377,984  78%    1.21MB/s    0:02:48 . Drive 1: most issues with https://termbin.com/j5m2   drive 2: https://termbin.com/kizsg
14:20:16 <Beladona> Now I can't even `ls` any part of any other drive or any system path either. and all what I said happens occasionally.  zpool status -v says ONLINE but even if it is dead, why I can't ls anywhere elsewher
14:20:17 <Beladona> The LS should have worked for other places. What is wrong with the stable freebsd here?
14:22:14 <CmdLnKid> your hardware
14:22:51 <Beladona> dock or drive ? but either way, why LS/ thunar stops system wide?
14:23:17 <CmdLnKid> because your io is locked doing something more intensive
14:23:31 <CmdLnKid> dock as in USB dock >
14:23:37 <Beladona> yes
14:23:54 <CmdLnKid> i would blame your problems on that
14:24:08 <Beladona> https://www.amazon.com/ORICO-Duplicator-Function-Protocol-Supported/dp/B00JJEUL5W
14:24:11 <VimDiesel> Title: Amazon.com: ORICO Dual Bay 2.5" 3.5" USB 3.0 to SATA Hard Drive Docking Station with Offline Duplicator and Clone Function [UASP Protocol and 2 x 12TB Supported]- 6629US3 : Everything Else
14:24:16 <CmdLnKid> i get that on different platforms other than freebsd
14:24:23 <CmdLnKid> and freebsd
14:24:36 <Beladona> ya but ls on other system paths should work
14:24:38 <Beladona> or not?
14:24:42 <Beladona> so its dock or the drive?
14:24:47 <CmdLnKid> rsync on usb for the longest time seems to overread
14:25:05 <CmdLnKid> or write and the buffer can't keep up making you wait
14:25:32 <CmdLnKid> moreso bandwidth caps with usb and the disk
14:26:46 <CmdLnKid> i can do the same thing on a macbook pro and my usb connected disk dock any time i want if i run rsync to it. and thats even a diff filesystem than what you are using
14:27:39 <CmdLnKid> seems it gets clogged between write/read speeds on the usb bus
14:28:04 <Beladona> i see
14:28:48 <CmdLnKid> if there is a way you can limit your write speeds with rsync id suggest it but id never looked into it
14:31:03 <CmdLnKid> i found this... a long time ago and could help you https://github.com/DataIX/main/blob/master/vendor/vehosting/slowdown.c
14:31:04 <VimDiesel> Title: main/vendor/vehosting/slowdown.c at master · DataIX/main · GitHub
14:32:27 <CueXXIII> rsync does have --bwlimit to limit the sync speed
14:32:36 <CmdLnKid> k
14:36:05 <Beladona> if I plug the hdd directly to systme sata, it will be online all the time. I don't want that
14:36:12 <Beladona> I only want to plug it in when making backups
14:36:20 <Beladona> any suggestions how to do / or disable the drive?
14:36:31 <Beladona> if I can't put it in docking station
14:37:34 <CmdLnKid> you can but im failing to remember what i did but think its something like camcontrol
14:38:27 <V_PauAmma_V> Beladona left.
14:38:48 <CmdLnKid> errr why am i not getting quit notices
14:39:04 <CmdLnKid> i was trying to figure it out the other day and can't locate it
14:39:25 <V_PauAmma_V> Which IRC client?
14:39:29 <CmdLnKid> irssi
14:39:38 <CmdLnKid> latest ver
14:39:58 <CmdLnKid> at some point recently it just stopped
14:40:18 <CmdLnKid> the same with /names being displayed on join
14:43:43 <CmdLnKid> even tho this config has not changed in ~ 5 years
14:43:47 <yuripv> /ignore
14:43:58 <CmdLnKid> oooh /me takes a look
14:44:16 <yuripv> wait, actually yes, names are not shown any longer
14:44:48 <CmdLnKid> yep but yuripv your right about ignores/ joins parts thanks
14:45:10 <CmdLnKid> dunno when i did that but yes /names are no longer shown on join
14:45:32 <CmdLnKid> that doesn't bother me so much tho
14:48:12 <CmdLnKid> eh!!! there was a quit
14:48:24 * CmdLnKid owes yuripv a beer
14:48:47 <vkarlsen> I think it shows /names only when joining small channels, but I don't know what the limit is
14:49:45 <CmdLnKid> nah its all channels
14:50:05 <vkarlsen> Ah: The NAMES list is now hidden by default if there are more than 18 users on the channel (an#7). To revert to the previous behaviour: /SET show_names_on_join_limit -1
14:50:18 <CmdLnKid> im on chans with 67 users and 600+
14:50:39 <CmdLnKid> wth
14:50:46 <CmdLnKid> where'd you find that
14:50:52 <V_PauAmma_V> This here channel has 649.
14:51:12 <vkarlsen> https://irssi.org/NEWS/#news-v1-4-1
14:51:14 <VimDiesel> Title: NEWS - IrssiMenuExpandLight modeDark modeAuto light/dark mode
14:51:36 <CmdLnKid> wholly shit
14:51:53 <CmdLnKid> the last place id look for that feature to be explained haha
14:52:23 * CmdLnKid is now starting a list of ppl i owe a beer
14:55:26 <CmdLnKid> surprising they set it so low
15:46:46 <antranigv> Hey all. I need a way to get a speed per IP. similar to `systat -ifstat` but per destination. any tools we have in base or ports?
15:59:54 <debdrup> net-mgmt/iftop
16:01:12 <debdrup> It dates back to the early 2000s and is a TUI thing, but it works pretty consistently because it's just relying on libpcap.
16:42:05 <andmars> hi, I'm trying to install st as my terminal but want to build it myself from the suckless.org website. It works fine with dwm and dmenu, using this forum post: https://forums.FreeBSD.org/threads/installing-dwm-manually-vs-pkg.74687/post-457030
16:42:06 <VimDiesel> Title: DWM - Installing dwm manually vs pkg | The FreeBSD Forums
16:42:36 <andmars> but with st I get an error: fatal error: 'ft2build.h' file not found
16:54:47 <andmars> installing pkgconf somehow did the trick for st
22:25:27 <SpaceBass> Anyone have a clever idea for setting the locale of a user without a shell?
22:25:58 <llua> a login class
22:26:28 <SpaceBass> Like in /etc/login.conf?
22:26:51 <llua> correct
22:27:16 <SpaceBass> I've got :lang=en_US.UTF-8 set there, but its not being applied to users
22:31:52 <checkpoint> # login.conf - login class capabilities database.
22:31:53 <checkpoint> #
22:31:53 <checkpoint> # Remember to rebuild the database after each change to this file:
22:31:53 <checkpoint> #
22:31:53 <checkpoint> #       cap_mkdb /etc/login.conf
22:31:55 <llua> did you run cap_mkdb?
22:32:11 <SpaceBass> Yes
22:32:28 <SpaceBass> Surely I don't have to reboot, right?
22:32:51 <checkpoint> you have to re-login
22:33:46 <SpaceBass> Im specifically trying to get this to apply to a user that is for a service only (no shell, no home)
22:34:19 <checkpoint> what login class ?
22:34:23 <SpaceBass> Guess I can bounce the box...
22:35:36 <checkpoint> for CGI scripts running from nginx it should be 'daemon' class, I guess
22:36:20 <SpaceBass> I remember how to change classes but not show them
22:37:37 <SpaceBass> Anyway... bounced the box and now my service user shows the right language ... but it didn't fix the underlying problem im working on
22:38:13 <llua> why didn't you just bounce the service?
22:39:11 <SpaceBass> Im not a smart man
22:40:54 <checkpoint> btw, "ps auxw -o class" can be used to learn current login class of a process
22:41:03 <SpaceBass> Helpful, thanks!
22:41:38 <SpaceBass> I think its a bug in the port relative to 14.0 ... ive been in touch with the maintainer but wanted to rule out everything on my end
23:50:39 <Kit_Leopold> Hello dear members of the chat. I have a rather general question for those people who use the operating system on their home computer. Can you please tell me what problems you faced while using the FreeBSD system? Maybe you were missing something that is available in Linux distributions and not in FreeBSD?
23:51:19 <llua> it hasn't make me a billion yet
23:51:25 <llua> made*
23:55:43 <V_PauAmma_V> I had some trouble making XFCE work until I 1- read the doc and 2- did what the doc said to do. That strikes me as a me problem, not a FreeBSD problem.
23:56:28 <Kit_Leopold> Thank you.
23:57:22 <V_PauAmma_V> (Step 2 is, unsurprisingly in hindsight, crucial.)