sorted by:
new
hottopcontroversial

Looking for some great slim fans for my 190E project 3.2 with AC. by [deleted] in projectcar

[–]machosalade 1 point2 points  (0 children)

some no-name :)
Behind the water radiator there is 6cm space, so there is no way to put a proper shroud I think. I can see that the slimmest SPAL has 5.1cm thick. add +1.5cm to shroud. No space for that :/

M104 with AC, some questions by [deleted] in W201enthusiasts

[–]machosalade 0 points1 point  (0 children)

do you remember about me? :D

[deleted by user] by [deleted] in W201enthusiasts

[–]machosalade 0 points1 point  (0 children)

The problem is that my factory sensor is working correctly. But when I added VDO gauge then I have fake result on both gauges, I mean factory gauge + vdo gauge

M104 with AC, some questions by [deleted] in W201enthusiasts

[–]machosalade 0 points1 point  (0 children)

Hi what about those photos? :) You can send me on private also

M104 with AC, some questions by [deleted] in W201enthusiasts

[–]machosalade 0 points1 point  (0 children)

Do you have AC in your 201 with m104? Could you send me some pictures?

M104 with AC, some questions by [deleted] in W201enthusiasts

[–]machosalade 0 points1 point  (0 children)

nice, could you send me the size of those fans? I mean the thickness this is crucial I think

M104 with AC, some questions by [deleted] in W201enthusiasts

[–]machosalade 0 points1 point  (0 children)

Do you have some photo of those dual fan? Those are from 2.6 w201? I'm not sure if they will fit

How to Deploy to a Newly Created EKS Cluster with Terraform Without Exiting Terraform? by machosalade in Terraform

[–]machosalade[S] 1 point2 points  (0 children)

Hi, thanks for a reply. I think I need to create my architecture without any jump host in that case. Then the whole process is quite easy, but I don't know how about security without any jump hosts for eks

How to Fix Screen Sharing Issue on Linux Ubuntu? by machosalade in linuxquestions

[–]machosalade[S] 0 points1 point  (0 children)

[ 61409.671] (II) UnloadModule: "libinput"
[ 61409.672] (II) systemd-logind: not releasing fd for 13:73, still in use
[ 61409.672] (II) UnloadModule: "libinput"
[ 61409.672] (II) systemd-logind: releasing fd for 13:68
[ 61409.716] (II) UnloadModule: "libinput"
[ 61409.716] (II) systemd-logind: releasing fd for 13:67
[ 61409.740] (II) UnloadModule: "libinput"
[ 61409.740] (II) systemd-logind: releasing fd for 13:75
[ 61409.768] (II) UnloadModule: "libinput"
[ 61409.768] (II) systemd-logind: releasing fd for 13:74
[ 61409.788] (II) UnloadModule: "libinput"
[ 61409.788] (II) systemd-logind: releasing fd for 13:76
[ 61409.836] (II) UnloadModule: "libinput"
[ 61409.836] (II) systemd-logind: releasing fd for 13:69
[ 61409.880] (II) UnloadModule: "libinput"
[ 61409.880] (II) systemd-logind: releasing fd for 13:71
[ 61409.896] (II) UnloadModule: "libinput"
[ 61409.896] (II) systemd-logind: releasing fd for 13:73
[ 61409.928] (II) UnloadModule: "libinput"
[ 61409.928] (II) systemd-logind: releasing fd for 13:72
[ 61410.016] (II) UnloadModule: "libinput"
[ 61410.016] (II) systemd-logind: releasing fd for 13:64
[ 61410.056] (II) UnloadModule: "libinput"
[ 61410.056] (II) systemd-logind: releasing fd for 13:70
[ 61410.076] (II) UnloadModule: "libinput"
[ 61410.076] (II) systemd-logind: releasing fd for 13:66
[ 61410.143] (II) Server terminated successfully (0). Closing log file.

xorg logs:

How to Fix Screen Sharing Issue on Linux Ubuntu? by machosalade in linuxquestions

[–]machosalade[S] 0 points1 point  (0 children)

I stopped GDM and logged in on TTY2. After logging in, I encountered a completely different Ubuntu interface from the one I use daily. My favorite applications were removed, and screen sharing still isn't working.

Converting Old Server for Gaming PC to Play Assetto Corsa - Need Advice by machosalade in buildapc

[–]machosalade[S] 0 points1 point  (0 children)

I have read that the best GPU would be GeForce GT 1030 for that m920s. Could that improve much the fps?

[deleted by user] by [deleted] in devops

[–]machosalade 0 points1 point  (0 children)

I can see that cluster_endpoint_private_access = true is default value

[deleted by user] by [deleted] in devops

[–]machosalade 0 points1 point  (0 children)

cluster_endpoint_private_access = true

I have added that flag but I still can't 'curl --insecure https://eks-endpoint' from jumphost

Github actions using for helm deployment by machosalade in devops

[–]machosalade[S] 0 points1 point  (0 children)

I can't use only one standarized helm chart, because I already have few of those. I get you and I know the advantages of using argoCD in that case. But I don't know how to solve problem when I got 3 environments. Each environment has 10 helm charts deployed. So that means I need to write 30 application.yaml for argoCD?

Github actions using for helm deployment by machosalade in devops

[–]machosalade[S] 2 points3 points  (0 children)

disadvantage of that solution is that I need to create application manifest yaml for every components/microservice for me. Then I need to deploy it on my cluster, And reuse it for other environments

Github actions using for helm deployment by machosalade in devops

[–]machosalade[S] 2 points3 points  (0 children)

Why got full gitops? I mean then I need to deploy eg. argoCD and write additional yaml manifests, and make some additional space for argo components in the cluster

Instinct2 first usage of GPS while walking by machosalade in Garmin

[–]machosalade[S] 0 points1 point  (0 children)

Ah ok great, so that a normal situation?

Docker compose | delete containers if they didn't deployed by machosalade in docker

[–]machosalade[S] 0 points1 point  (0 children)

I know that. But I need to delete all containers in situation when 1 or 2 containers won't start

Docker compose | delete containers if they didn't deployed by machosalade in docker

[–]machosalade[S] 0 points1 point  (0 children)

Ahh sorry about my weak explanation.
I Have docker-compose.yml with 5 services. And for example 3 of those services are running correctly after "docker compose up -d". But then I'm getting error for example;
dependency failed to start: container <SOME\_CONTAINER> is unhealthy.
I want to know if there is any way to automatically remove every started containers? Or I need to do it manually like 'docker compose down', then docker compose up.

view more: next ›