From owner-freebsd-hackers@freebsd.org Thu Mar 2 19:29:47 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F111CF6EB0; Thu, 2 Mar 2017 19:29:47 +0000 (UTC) (envelope-from subbsd@gmail.com) Received: from mail-qk0-x241.google.com (mail-qk0-x241.google.com [IPv6:2607:f8b0:400d:c09::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3C5206B9; Thu, 2 Mar 2017 19:29:47 +0000 (UTC) (envelope-from subbsd@gmail.com) Received: by mail-qk0-x241.google.com with SMTP id n127so21603565qkf.2; Thu, 02 Mar 2017 11:29:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=/kTCpRDCRzXFw03gpduEMR7SymZLLB/5IaZ8YA7oYTw=; b=CMD4YWo+Z+3T5/oZxbaMkXICXrHesstkiETQfcOIz87CU31q7RKtzDX7D6FsF4353N s0EQX6MpUX96xclWcxNMMfZVBEvLmO2JTlbBercZ5hgu7oz/suskYZHuBkonfp0VLxkY WpLTcuRobHeZCbg4+hjrnxZJ9bly6fi+cBzZm5xVsRrwxbQHdfzo3Y3JHwtPNyftBC/s tla/Vogsm0wwguX6BGnQWGrjx0GqCx+SSAQdwdZt8OfysSV4Vaev8zSmSaYDYKjJMKf4 x+FYOe4peeD8u8Z/DgdnIQdIo9MtCTEx9ksOhhEGdodu6qPyrLgDkiX2+iMPsZzG3n3N o9lw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=/kTCpRDCRzXFw03gpduEMR7SymZLLB/5IaZ8YA7oYTw=; b=dxgtsbEItspPwIf5obgWB32xqIert4+l6JW5h6CdbcUdqbRcohk7QjB5gwSvLAe49S yhB+9xnfqvjl32gVpNdqQ9PCo1sH4/bjIiTorZ92pWEHko7tmf01cTgC2MStAttPmgSk ScZ6bRJwCST15edUerLKLpMkkulSVTSRUp0XcpT7lv6ETigr8k1ya9i5sijYnKtBz5TS TPVxnvJOWMy/6gEo3ufchJXh22PyjVzijvx+vJCh/k60n/DPprJA4ywmSTnLaA05MBZm LDWVRNxBieEMXuOGgi5hNlvztPRGY185OM2vbzp53rUfIA6oLb5WxY8i7oJxKz5vigI8 ra9g== X-Gm-Message-State: AMke39mkQbZDD8IXIPnYGOxCsA2dI9dJ4Wq1HIOfSGntFax/92wXykUnE+p+MnAO7TkPh+NwTKlmTYWHkTXORw== X-Received: by 10.55.212.206 with SMTP id s75mr18199752qks.71.1488482986309; Thu, 02 Mar 2017 11:29:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.134.70 with HTTP; Thu, 2 Mar 2017 11:29:46 -0800 (PST) From: Subbsd Date: Thu, 2 Mar 2017 22:29:46 +0300 Message-ID: Subject: effect of strip(1) on du(1) To: freebsd-current Current , freebsd-hackers Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Mar 2017 19:29:47 -0000 Hi, Not sure for FreeBSD < 12, but i found interesting behavior strip effect(1) on du(1) command: -- % strip /bin/pax && sleep 4 && du -sh /bin/pax 65K /bin/pax % strip /bin/pax && sleep 3 && du -sh /bin/pax 65K /bin/pax % strip /bin/pax && sleep 2 && du -sh /bin/pax 512B /bin/pax % strip /bin/pax && sleep 3 && du -sh /bin/pax 65K /bin/pax -- During some interval after strip call, du will show 512B for any file. If execute du(1) after strip(1) without delay, this behavior is reproduced 100%: % strip /bin/sh && du /bin/sh 1 /bin/sh What such behavior is connected with?