00:52:47 <rtprio> bonjour is overrated
00:57:53 <babz> what happened to politeness?
01:01:03 <rtprio> there's nothing impolite about calling something overrated; also, printers are the worst
01:01:36 <tmp_> Printers are my nemesis.
02:07:29 <thedaemon_> if there is a hell, printers come from it.
02:09:22 <Melon> anything else but those printers
02:17:25 <Exclamation-Poin> thedaemon_, you wanna get rid of cups too and just cant, huh
02:17:26 <Exclamation-Poin> ?
02:21:31 <voy4g3r2> as it comes to printers, i just want a simple txt file to print "properly and not do the steps print out <line 1> \n \t \t \t <line 2> \n \t\t\t <line3>
02:26:11 <Beladona> poddo:  I wonder that if you are not getting that luajit issue, then why I am?
02:50:19 <thedaemon> I don't print at home Exclamation-Point
11:35:59 <meena> so, now that we have an official PkgBase repo, should I just redirect my domain to it…?
12:52:18 <adilix> hi all
13:41:19 <CrtxReavr> Printers are okay.
13:41:32 <CrtxReavr> It's supporting people who use them that sucks.
13:44:53 <CrtxReavr> This will contradict what I just said, but just a couple days ago, my wife was trying to print this one PDF file to our networked HP LaserJet (PCL 5).
13:45:17 <CrtxReavr> And everytime she'd try to print it, it'd spit out a piece of paper with a PCL error on it.
13:45:27 <CrtxReavr> She could view the PDF file file.
13:45:33 <CrtxReavr> er fine
13:45:42 <CrtxReavr> She could print other PDF files.
13:45:51 <CrtxReavr> She could print that one PDF file to other printers.
13:45:54 <voy4g3r2> death to the printer snafus
13:46:18 <voy4g3r2> i have experienced that issue when everyone else can print, bsd, linux, mac os, iphone.. then lets bring in a windows 10 laptop.. boom epic fail!
13:46:40 <CrtxReavr> I have to assume that file exploited some PCL bug in the printer's firmware.
13:48:36 <CrtxReavr> Normally I like dealing with PDF files, 'cause they always print consistantly.
13:49:14 <CrtxReavr> Whereas Word docs for instance, can render and print quite differently, depending on which fonts are installed on the system.
13:51:17 <voy4g3r2> yeah
13:52:45 <CrtxReavr> Falling back to a default font is one thing, but it can completely mess up pagination.
13:53:09 <CrtxReavr> (Which is why I *HATE* it when recruiters ask for my resume as a Word doc.)
13:55:23 <ZedHedTed> i've seen certain PDFs fail to print fully unless you print them from crudobe acrobat reader, on macOS at least.
15:04:26 <cedb> man ive just been tracking main for a little bit and havent managed to completely obliterate my data, being a freebsd noob i gotta say
15:04:44 <cedb> kuddos to whoever is amongst those  slinging those patches around
18:44:49 <FreeBDSM> does anyone know how to use 'date' on macos to convert time in seconds into formatted string HH:MM:SS? like `date ... 64 ...` should yield `00:01:04`?
19:04:43 <tmp_> It'd be the same as on FreeBSD. Using your example: date -ujr 64 +%T
19:05:30 <meena> cedb: usually we pick up pretty quickly when there's data destroying going on in main
19:08:13 <cedb> data destroying?
19:08:37 <cedb> meena: you mean poudriere nuking everything cause it couldnt build tex-fmt or soemthing else?
19:12:01 <cedb> oh while im here quick question i cant reinstall nginx after my latest install i get 'pkg: Fail to rename /usr/local/etc/ssl/.pkgtemp.certs.OepkH7YtzTP4 -> /usr/local/etc/ssl/certs:Is a directory' im not sure like why it even sgned with a symlink in the first place its been doing this for a while now, usually just relaunching bulk would fix it
19:23:08 <meena> cedb: which of the two is a director?
19:23:34 <meena> *directory
19:25:31 <cedb> meena: certs of course thats where my very private stuff  is
19:30:35 <nimaje> cedb: so with main you meant ports/main and not src/main?
19:31:26 <cedb> current and main for the ports
19:31:34 <cedb> i meant more "current"
19:38:02 <nimaje> I asked because of "you mean poudriere nuking everything cause it couldnt build tex-fmt or soemthing else?" (indicating the ports tree, so ports/main), but that scenario doesn't match "completely obliterate my data" (which indicates the base system, so src/main)
20:09:30 <cedb> oh no it doesnt completely obliterate my data
20:10:26 <cedb> it just doesnt sign the results properly if theres some random failure, i think that was cause i rebuilt but with libressl in some places and it choked on it or soemtihng
20:31:07 <rtprio> how do i diagnose my server rebooting itself
20:31:48 <rtprio> there's nothing discernable in the logs
20:32:39 <rtprio> it happend when i put a different sata controller into it
20:33:30 <otis> log physical console output, if possible
20:34:20 <jimmiejaz> a number of posts are saying it's chatGPT
20:36:54 <rtprio> otis: the server is 8000km away
20:37:01 <jimmiejaz> https://www.instagram.com/p/CzG7WAFLicE/?utm_source=ig_embed&utm_campaign=loading  may have started here
20:37:02 <VimDiesel`> Title: ZeroBlogThirty on Instagram: "Centcom canceled their Ball. Never thought we’d see the day"
20:38:15 <jimmiejaz> sorry. wrong channel.
20:43:45 <otis> rtprio: no ipmi on it?
20:44:11 <rtprio> no
20:44:23 <rtprio> it's a 10 year old supermicro in my 'homelab'
20:46:01 <rtprio> it seems sporatic, up to 9-12 days, sometimes as often as a day or two.  it's serving nfs, samba. there's nothign espically taxing on it.
20:47:59 <dkeav> a lot of times its a failing PSU when its sporadic like that
20:48:59 <otis> rtprio: send syslog (*.*) to other host
20:51:20 <rtprio> dkeav: it does have two PSU
20:51:36 <rtprio> otis: that's a good idea; perhaps the last log isn't getting written ?
20:51:58 <dkeav> pop one out, and see if stops, if happens again, switch which one is popped out
20:52:10 <dkeav> if both do it, then probably not the issue
20:52:19 <rtprio> if i pop one out, it beeps.
20:52:23 <rtprio> could it be a bad drive?
20:52:36 <rtprio> nothing in the logs about that, and 2 zpools
20:56:18 <foxiepaws> check the bios logs
20:56:54 <foxiepaws> usually they can give notes on unexpected poweroff from PSU failure
20:57:06 <foxiepaws> hence the ipmi recommendation
20:57:11 <foxiepaws> because it'll do the same
21:01:56 <rtprio> seems curious that the PSU is deciding to fail after i had the case open
21:05:02 <rtprio> but ok
21:05:34 <rtprio> i'll start with the *.* remote syslog and try to get my remote hands to diagnose the PS
21:11:19 <foxiepaws> the remote syslog is a great idea and should help a lot, but it might not catch certain kinds of panics.
21:14:22 <foxiepaws> I did have an issue with my dying RAID card a long time ago that it just randomly rebooted and there was no evidence of it, i just happened to catch it one night while gaming lol
21:14:49 <foxiepaws> hopefully it's not that kind of thing though, because it's hellish to catch
21:18:05 <rtprio> foxiepaws: sadly i took the old raid card out because freebsd dropped support for it, and i needed 2 more sata ports
21:18:13 <rtprio> so i have this generic one in it
21:18:22 <rtprio> that's when the issues started,
21:41:16 <GeoBarRod> Hi community. Please, I need a command line that joins the lines of 2 files interleaved to a new file.
21:41:17 <GeoBarRod> lines of file_1:
21:41:17 <GeoBarRod> 1
21:41:17 <GeoBarRod> 3
21:41:17 <GeoBarRod> 5
21:41:17 <GeoBarRod> lines of file_2:
21:41:19 <GeoBarRod> 2
21:41:21 <GeoBarRod> 4
21:41:23 <GeoBarRod> 6
21:41:25 <GeoBarRod> new file_3:
21:41:27 <GeoBarRod> 1
21:41:31 <GeoBarRod> 2
21:41:33 <GeoBarRod> 3
21:41:35 <GeoBarRod> 4
21:41:37 <GeoBarRod> 5
21:41:39 <GeoBarRod> 6
21:49:58 <hackerman> How does one create a rule that exectutes for every file in a certain directory
21:50:30 <hackerman> in bsdmake...
22:13:41 <mason> !pastebin