<tune>I'm no longer sure what to do. I installed lm-sensors and I can see that during the choppy playback it gets to like 96c
<nckx>tune: But first you need to actually look at your CPU frequency statistics to find out what's really happening, and sensors to see the temp. Maybe a bogus BIOS limit (processor.ignore_ppc=1 on the kernel command line could help). Maybe setting the governor to ‘performance’ at max frequency will make a difference. All that said, if your CPU is throttling, it's probably for a reason. It's too hot. End of ☹
<tune>probably can't afford to get much hotter than that. it cools down a lot after being paused for a bit. never had issues like this with movies before
<nckx>tune: My i7-3520M goes up to 100°C, although I throttle it at 75. IMO running at 96 for long periods of time is not going to make your CPU last very long.
<tune>sure, but I don't understand why it's struggling so much more than usual
<tune>kinda makes me wanna throw the computer away. I don't think I'm asking that much of it
<nckx>tune: Slim chance, but… if you happen to have an i915-compatible GPU, I recently added libva acceleration support.
<nckx>tune: What kind of CPU & video file are we talking?
<nckx>My 7-year-old laptop CPU handles 1080p x265/HEVC just fine. Did you accidentally all the 4K? 😛
<rekado>civodul: on berlin I’ve got a custom Cuirass package definition (to test minor things), so if you want to avoid having to update the ‘cuirass’ package all the time just adjust that custom package in berlin.scm
<rekado>I substituted (compose …) with ‘derivation-log-file’, but I didn’t escape the parens in the match expression.
<rekado>either way it’s wrong. There shouldn’t be any substitution anyway.
<rekado>but there’s still a problem in src/cuirass/templates.scm, ‘build-details’.
<rekado>we apply ‘derivation-input-path’ which leads to this error: In procedure derivation-input-derivation: Wrong type argument: #<derivation /gnu/store/9cagf3a66v132dbvgla725mfvmvnbhjn-linux-libre-5.2.7-guix.tar.xz.drv => /gnu/store/2bhq99srvy93jqn9iwswjddii194za1x-linux-libre-5.2.7-guix.tar.xz 17344b0>
<civodul>rekado: also, cuirass-web is running but cuirass is not
<apteryx>hello! could someone point me to where the magic happens when doing 'docker start guix-image-id'? What command does it run to initialize shepherd and the system?
<apteryx>(with a guix docker image created using 'guix system docker-image my-config.scm')
<civodul>apteryx: there's an "entry point" in the image, and that entry point is the shepherd
<civodul>so it basically runs the shepherd as in a normal system
<civodul>see 'system-docker-image' in (gnu system vm)
<apteryx>Thank you! I'll check that module. So the shepherd is run upon doing 'docker start $container_id'
<apteryx>in a real usage context, one would probably fire up the container, then run a command in it (in an automated manner). How do I know when shepherd has completed its initualization?
<apteryx>example: docker start $container_id && docker exec -ti $container_id /run/current-system/profile/bin/bash --login -c 'herd status' returns: error: connect: /var/run/shepherd/socket: No such file or directory when the system is not yet initialized (that's my brute force way of telling for now)
<civodul>apteryx: good question, you could run "herd status" until it succeeds
<civodul>or we could change the entry point such that it returns once shepherd is up and running
<civodul>it's tricky to do though because the process started by "docker run" is PID 1 inside the container
<roptat>but I'm not even sure I can manage to get /gnu created
<apteryx>so, I think I could try to Guilify my bash entrypoint, and use it a the default entrypoint boot-program (in the built docker image metadata directly). That'd fix the 'docker run -ti --rm some-command' common use case.
<quiliro>Minall: civodul diris vin ke kiel ne estas aserteco, ĝi estas demando!
<quiliro>Minall: vi skribu "Kiel vi fartas?", ne "Kiel vi fartas!".
<quiliro>is there a template file to build an email server with spam and virus control as well as all other necesary configurations for it to be accepted by other email servers such as gmail, hotmail, yahoo, etc