
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Chaos and Order</title>
      <link>https://www.youngju.dev/blog</link>
      <description>천천히 올바르게. AI Researcher &amp; DevOps Engineer Youngju&#39;s blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, and data engineering — plus mindset essays on confidence, routines, health, and sport psychology.</description>
      <language>ko</language>
      <managingEditor>fjvbn2003@gmail.com (Youngju Kim)</managingEditor>
      <webMaster>fjvbn2003@gmail.com (Youngju Kim)</webMaster>
      <lastBuildDate>Sat, 15 Aug 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/운영/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/database/2026-08-15-guide-bulk-data-processing</guid>
    <title>대용량 데이터 처리 완전 가이드: COPY, 청크 배치, 그리고 되돌릴 수 있는 작업</title>
    <link>https://www.youngju.dev/blog/database/2026-08-15-guide-bulk-data-processing</link>
    <description>PostgreSQL 18에서 수억 행을 적재하고 갱신하고 삭제하는 작업을 안전하게 수행하는 방법을 정리합니다. COPY의 옵션과 기본값, 문서가 권장하는 초기 적재 절차, ON_ERROR로 불량 행을 견디는 방법, 대량 UPDATE와 DELETE를 청크로 나누는 설계, 삭제 이후의 죽은 행 처리와 VACUUM FULL을 피해야 하는 이유, 그리고 재개 가능한 백필 작업을 만드는 방법까지 다룹니다.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>데이터베이스</category><category>postgresql</category><category>배치처리</category><category>데이터적재</category><category>운영</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/database/2026-08-15-guide-connection-pool</guid>
    <title>커넥션 풀 완전 가이드: 풀링 모드가 애플리케이션과 맺는 계약</title>
    <link>https://www.youngju.dev/blog/database/2026-08-15-guide-connection-pool</link>
    <description>PostgreSQL 18과 PgBouncer를 기준으로 커넥션 풀을 계약의 관점에서 정리합니다. 세션·트랜잭션·문장 풀링 세 가지 모드가 각각 무엇을 보장하고 무엇을 포기하는지, 트랜잭션 풀링에서 준비된 문장과 SET, LISTEN/NOTIFY, 어드바이저리 락이 왜 깨지는지, 애플리케이션 풀과 PgBouncer와 max_connections 사이의 삼중 예산을 어떻게 배분하는지, 그리고 타임아웃을 어느 계층에 걸어야 하는지를 문서의 기본값과 함께 다룹니다.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>데이터베이스</category><category>postgresql</category><category>pgbouncer</category><category>커넥션풀</category><category>운영</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/database/2026-08-15-guide-db-performance-tuning</guid>
    <title>DB 성능 튜닝 완전 가이드: 파라미터를 만지기 전에 측정하는 순서</title>
    <link>https://www.youngju.dev/blog/database/2026-08-15-guide-db-performance-tuning</link>
    <description>PostgreSQL 18을 기준으로 성능 튜닝을 파라미터 목록이 아니라 진단 순서로 정리합니다. pg_stat_statements로 워크로드를 프로파일링하고, 대기 이벤트로 병목의 성격을 가르고, 캐시와 I/O 지표를 읽고, 그다음에야 메모리 예산과 체크포인트와 autovacuum을 조정하는 순서입니다. PostgreSQL 18에서 바뀐 기본값들과 변경 전후를 비교하는 방법까지 다룹니다.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>데이터베이스</category><category>postgresql</category><category>성능튜닝</category><category>모니터링</category><category>운영</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/database/2026-08-15-guide-postgres-index</guid>
    <title>PostgreSQL 인덱스 완전 가이드: 설계부터 폐기까지 인덱스의 수명 주기</title>
    <link>https://www.youngju.dev/blog/database/2026-08-15-guide-postgres-index</link>
    <description>PostgreSQL 18을 기준으로 인덱스를 하나의 운영 자산으로 다룹니다. 어떤 컬럼을 어떤 순서로 넣을지 정하는 설계, 여섯 가지 인덱스 방식 중 하나를 고르는 판단, CONCURRENTLY로 안전하게 만드는 절차와 실패 복구, 정말 쓰이는지 확인하는 검증, 부풀어 오른 인덱스를 다시 만드는 운영, 그리고 되돌릴 수 있게 폐기하는 방법까지 수명 주기 순서로 정리합니다.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>데이터베이스</category><category>postgresql</category><category>인덱스</category><category>성능튜닝</category><category>운영</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-backup-and-restore.en</guid>
    <title>The complete backup and restore guide: designing backwards from the recovery scenario</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-backup-and-restore.en</link>
    <description>Starting from RPO and RTO, the criteria for choosing between rsync, tar, LVM snapshots, and snapshot-based backup tools. Covers the recovery rehearsal procedure and the five ways a backup quietly rots.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>백업</category><category>복구</category><category>재해복구</category><category>운영</category><category>rsync</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-backup-and-restore.ja</guid>
    <title>バックアップとリストア完全ガイド: 復旧シナリオから逆算して設計する</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-backup-and-restore.ja</link>
    <description>RPOとRTOから出発して、rsync、tar、LVMスナップショット、スナップショットベースのバックアップツールを選ぶ基準を整理します。復旧リハーサルの手順と、バックアップが静かに壊れる五つの方式まで扱います。</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>백업</category><category>복구</category><category>재해복구</category><category>운영</category><category>rsync</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-backup-and-restore</guid>
    <title>백업과 복구 완전 가이드: 복구 시나리오에서 거꾸로 설계하기</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-backup-and-restore</link>
    <description>RPO와 RTO에서 출발해 rsync, tar, LVM 스냅샷, 스냅샷 기반 백업 도구를 고르는 기준을 정리합니다. 복구 리허설 절차와 백업이 조용히 망가지는 다섯 가지 방식까지 다룹니다.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>백업</category><category>복구</category><category>재해복구</category><category>운영</category><category>rsync</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-dns.en</guid>
    <title>The Complete Guide to DNS: Following a Name All the Way to an Address</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-dns.en</link>
    <description>Splits name resolution into five separate segments — stub resolver through authoritative server — and works through record types, TTL and caching, delegation, reading dig output, propagation delay and stale caches, DNSSEC, and running DNS inside a company. Every command and rule here was checked against the RFC text and the manual pages.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>dns</category><category>네트워크</category><category>운영</category><category>트러블슈팅</category><category>dig</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-dns.ja</guid>
    <title>DNS 完全ガイド: 名前がアドレスになる経路を最後までたどる</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-dns.ja</link>
    <description>スタブリゾルバーから権威サーバーまで、名前解決の経路を区間ごとに分けたうえで、レコードタイプと TTL、委任、dig の読み方、伝播遅延とスタイルキャッシュ、DNSSEC、社内 DNS の運用までを整理します。コマンドとルールは RFC 原文とマニュアルで確認したものだけを載せました。</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>dns</category><category>네트워크</category><category>운영</category><category>트러블슈팅</category><category>dig</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-dns</guid>
    <title>DNS 완전 가이드: 이름이 주소가 되는 경로를 끝까지 따라가기</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-dns</link>
    <description>스텁 리졸버부터 권한 서버까지 이름 해석 경로를 구간별로 나누고, 레코드 타입과 TTL, 위임, dig 출력 해석, 전파 지연과 스테일 캐시, DNSSEC, 사내 DNS 운영까지 정리합니다. 명령과 규칙은 RFC 원문과 매뉴얼에서 확인한 것만 실었습니다.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>dns</category><category>네트워크</category><category>운영</category><category>트러블슈팅</category><category>dig</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-file-descriptors-and-inodes.en</guid>
    <title>A Complete Guide to File Descriptors and Inodes: What Happens When df and du Disagree</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-file-descriptors-and-inodes.en</link>
    <description>Starts from the relationship between inodes and directory entries and works through hard links, deleted-but-still-open files, inode exhaustion, and file descriptor limits. Covers why df and du diverge and how to recover, command by command.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>파일시스템</category><category>inode</category><category>파일디스크립터</category><category>운영</category><category>트러블슈팅</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-file-descriptors-and-inodes.ja</guid>
    <title>ファイルディスクリプタと inode 完全ガイド: df と du が食い違うとき何が起きているのか</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-file-descriptors-and-inodes.ja</link>
    <description>inode とディレクトリエントリの関係から出発して、ハードリンク、削除された開きっぱなしのファイル、inode の枯渇、ファイルディスクリプタの上限までを整理します。df と du が食い違う理由と復旧方法をコマンド単位で扱います。</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>파일시스템</category><category>inode</category><category>파일디스크립터</category><category>운영</category><category>트러블슈팅</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-file-descriptors-and-inodes</guid>
    <title>파일 디스크립터와 inode 완전 가이드: df와 du가 다를 때 무슨 일이 벌어지는가</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-file-descriptors-and-inodes</link>
    <description>inode와 디렉터리 엔트리의 관계에서 출발해 하드 링크, 삭제된 열린 파일, inode 고갈, 파일 디스크립터 한도까지 정리합니다. df와 du가 어긋나는 이유와 복구 방법을 명령 단위로 다룹니다.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>파일시스템</category><category>inode</category><category>파일디스크립터</category><category>운영</category><category>트러블슈팅</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-git-undo.en</guid>
    <title>Undoing Things in Git, the Complete Guide: What Comes Back and What Is Gone Forever</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-git-undo.en</link>
    <description>Maps the boundary between reset, revert, restore, reflog, and fsck by what can actually be recovered. Covers reflog expiry policy, when gc really deletes objects, force-push accidents, and worktree and submodule situations.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>git</category><category>버전관리</category><category>복구</category><category>운영</category><category>협업</category><category>명령어</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-git-undo.ja</guid>
    <title>Git 取り消し完全ガイド: 復元できるものと永遠に消えるもの</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-git-undo.ja</link>
    <description>reset、revert、restore、reflog、fsck の境界線を復元可能性という基準で整理します。reflog の期限切れポリシーと gc が実際にオブジェクトを削除するタイミング、強制プッシュ事故やワークツリー・サブモジュールの状況まで扱います。</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>git</category><category>버전관리</category><category>복구</category><category>운영</category><category>협업</category><category>명령어</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-git-undo</guid>
    <title>Git 되돌리기 완전 가이드: 복구되는 것과 영원히 사라지는 것</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-git-undo</link>
    <description>reset, revert, restore, reflog, fsck의 경계선을 복구 가능성 기준으로 정리합니다. reflog 만료 정책과 gc가 언제 객체를 실제로 지우는지, 강제 푸시 사고와 워크트리·서브모듈 상황까지 다룹니다.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>git</category><category>버전관리</category><category>복구</category><category>운영</category><category>협업</category><category>명령어</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-performance-tools.en</guid>
    <title>A Complete Guide to Linux Performance Tools: How to Read the Numbers in the Output</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-performance-tools.en</link>
    <description>Interprets the numbers printed by top, vmstat, iostat, pidstat, sar and perf one column at a time. Covers which tool answers which question, which values create optical illusions, and the order in which to choose a tool using the USE method.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>성능</category><category>모니터링</category><category>운영</category><category>sysstat</category><category>명령어</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-performance-tools.ja</guid>
    <title>Linux性能ツール完全ガイド: 出力の数字を解釈する方法</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-performance-tools.ja</link>
    <description>top、vmstat、iostat、pidstat、sar、perf が出力する数字を 1 列ずつ解釈します。どのツールがどの質問に答えるのか、どの値が錯覚を起こすのか、USE 方法論でツールを選ぶ順番までを整理しました。</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>성능</category><category>모니터링</category><category>운영</category><category>sysstat</category><category>명령어</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-performance-tools</guid>
    <title>리눅스 성능 도구 완전 가이드: 출력의 숫자를 해석하는 법</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-performance-tools</link>
    <description>top, vmstat, iostat, pidstat, sar, perf가 찍어 주는 숫자를 한 열씩 해석합니다. 어떤 도구가 어떤 질문에 답하는지, 어떤 값이 착시를 일으키는지, USE 방법론으로 도구를 고르는 순서까지 정리했습니다.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>성능</category><category>모니터링</category><category>운영</category><category>sysstat</category><category>명령어</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-troubleshooting-commands.en</guid>
    <title>The complete Linux troubleshooting command guide: from the first 60 seconds to root cause</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-troubleshooting-commands.en</link>
    <description>The diagnostic commands to run, in order, from the moment someone tells you a server is misbehaving. uptime, top, free, df, iostat, ss, journalctl — which number in each output to read, and what that number rules out versus what it leaves standing.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>트러블슈팅</category><category>운영</category><category>장애대응</category><category>명령어</category><category>성능</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-troubleshooting-commands.ja</guid>
    <title>Linux障害対応コマンド完全ガイド: 最初の60秒から根本原因まで</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-troubleshooting-commands.ja</link>
    <description>サーバーの様子がおかしいと連絡を受けた瞬間から順番に実行する診断コマンドを整理します。uptime、top、free、df、iostat、ss、journalctlまで、各出力のどの数字を見るべきか、その数字が何を除外して何を残すのかを説明します。</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>트러블슈팅</category><category>운영</category><category>장애대응</category><category>명령어</category><category>성능</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-troubleshooting-commands</guid>
    <title>리눅스 장애 대응 명령어 완전 가이드: 첫 60초부터 근본 원인까지</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-troubleshooting-commands</link>
    <description>서버가 이상하다는 연락을 받은 순간부터 순서대로 실행하는 진단 명령어를 정리합니다. uptime, top, free, df, iostat, ss, journalctl까지 각 출력의 어느 숫자를 봐야 하는지, 그 숫자가 무엇을 배제하고 무엇을 남기는지 설명합니다.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>트러블슈팅</category><category>운영</category><category>장애대응</category><category>명령어</category><category>성능</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-logging-design.en</guid>
    <title>The complete guide to Linux log operations: tying journald, rsyslog, and logrotate into one system</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-logging-design.en</link>
    <description>Designing the log plumbing of a Linux host, from journal retention policy to forwarding into rsyslog to the rotation modes of logrotate. Sets out the criteria for keeping the records an incident investigation needs without filling the disk.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>로그</category><category>journald</category><category>rsyslog</category><category>logrotate</category><category>운영</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-logging-design.ja</guid>
    <title>Linux ログ運用完全ガイド: journald、rsyslog、logrotate をひとつにつなぐ</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-logging-design.ja</link>
    <description>ジャーナルの保存ポリシー、rsyslog への転送、logrotate のローテーション方式まで、Linux ホストのログ配管を設計します。ディスクを埋めずに障害調査に必要な記録を残すための基準を整理します。</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>로그</category><category>journald</category><category>rsyslog</category><category>logrotate</category><category>운영</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-logging-design</guid>
    <title>리눅스 로그 운영 완전 가이드: journald, rsyslog, logrotate를 하나로 엮기</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-logging-design</link>
    <description>저널의 보존 정책, rsyslog로의 전달, logrotate의 회전 방식까지 리눅스 호스트의 로그 배관을 설계합니다. 디스크를 채우지 않으면서 장애 조사에 필요한 기록을 남기는 기준을 정리합니다.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>로그</category><category>journald</category><category>rsyslog</category><category>logrotate</category><category>운영</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-process-and-signals.en</guid>
    <title>Processes and Signals, the Complete Guide: Tracing Why a Process Will Not Exit</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-process-and-signals.en</link>
    <description>Signal numbers and default actions, the difference between SIGTERM and SIGKILL, zombies and orphans, process groups and sessions, nohup and setsid, and how to design a graceful shutdown. Traces the cause of a process that refuses to die, one layer at a time.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>프로세스</category><category>시그널</category><category>운영</category><category>커널</category><category>명령어</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-process-and-signals.ja</guid>
    <title>プロセスとシグナル完全ガイド: 終了しない理由を最後まで追跡する</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-process-and-signals.ja</link>
    <description>シグナル番号と既定動作、SIGTERM と SIGKILL の違い、ゾンビと孤児、プロセスグループとセッション、nohup と setsid、そしてグレースフルシャットダウンを設計する方法までを整理します。死なないプロセスの原因を階層ごとに追跡します。</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>프로세스</category><category>시그널</category><category>운영</category><category>커널</category><category>명령어</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-process-and-signals</guid>
    <title>프로세스와 시그널 완전 가이드: 종료가 안 되는 이유를 끝까지 추적하기</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-process-and-signals</link>
    <description>시그널 번호와 기본 동작, SIGTERM과 SIGKILL의 차이, 좀비와 고아, 프로세스 그룹과 세션, nohup과 setsid, 그리고 우아한 종료를 설계하는 방법까지 정리합니다. 죽지 않는 프로세스의 원인을 계층별로 추적합니다.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>프로세스</category><category>시그널</category><category>운영</category><category>커널</category><category>명령어</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-ssh.en</guid>
    <title>The complete guide to SSH operations: from key management to hardening a server without locking yourself out</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-ssh.en</link>
    <description>sshd_config hardening, choosing and distributing key types, ProxyJump and port forwarding, and the layered order to debug a connection that will not come up, organised from an operator viewpoint. Includes the procedure that keeps you from locking yourself out while changing configuration.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>ssh</category><category>보안</category><category>운영</category><category>서버관리</category><category>네트워크</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-ssh.ja</guid>
    <title>SSH運用完全ガイド: 鍵の管理からロックアウト事故のないサーバーハードニングまで</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-ssh.ja</link>
    <description>sshd_config のハードニング、鍵の種類の選択と配布、ProxyJump とポートフォワーディング、接続できないときのデバッグ順序までを運用者の視点で整理します。設定を変更している最中に自分自身をロックアウトしないための手順も含みます。</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>ssh</category><category>보안</category><category>운영</category><category>서버관리</category><category>네트워크</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-ssh</guid>
    <title>SSH 운영 완전 가이드: 키 관리부터 잠금 사고 없는 서버 하드닝까지</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-ssh</link>
    <description>sshd_config 하드닝, 키 종류 선택과 배포, ProxyJump와 포트 포워딩, 접속이 안 될 때의 디버깅 순서까지 운영자 관점에서 정리합니다. 설정을 바꾸다 스스로 잠기지 않는 절차를 포함합니다.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>ssh</category><category>보안</category><category>운영</category><category>서버관리</category><category>네트워크</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-tls-certificates.en</guid>
    <title>The Complete Guide to TLS Certificates: Handling Them End to End with openssl</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-tls-certificates.en</link>
    <description>A purpose-by-purpose reference of the openssl commands for reading certificates, creating CSRs, verifying chains, converting formats, and diagnosing server connections. Also covers how to identify expiry, a missing chain, and a key mismatch in the field.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>tls</category><category>인증서</category><category>openssl</category><category>보안</category><category>운영</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-tls-certificates.ja</guid>
    <title>TLS証明書完全ガイド: opensslコマンドで最後まで扱う</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-tls-certificates.ja</link>
    <description>証明書を読み、CSRを作り、チェーンを検証し、形式を変換し、サーバー接続を診断するopensslコマンドを目的別に整理します。有効期限切れとチェーン欠落、鍵の不一致を現場で判別する方法まで扱います。</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>tls</category><category>인증서</category><category>openssl</category><category>보안</category><category>운영</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-tls-certificates</guid>
    <title>TLS 인증서 완전 가이드: openssl 명령으로 끝까지 다루기</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-tls-certificates</link>
    <description>인증서를 읽고, CSR을 만들고, 체인을 검증하고, 형식을 변환하고, 서버 연결을 진단하는 openssl 명령을 목적별로 정리합니다. 만료와 체인 누락, 키 불일치를 현장에서 판별하는 방법까지 다룹니다.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>tls</category><category>인증서</category><category>openssl</category><category>보안</category><category>운영</category>
  </item>

    </channel>
  </rss>
