Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.unix.shell > #4489

Re: empty file is simply an inode with sort of null pointers

From Stephane Chazelas <stephane_chazelas@yahoo.fr>
Newsgroups comp.unix.shell
Subject Re: empty file is simply an inode with sort of null pointers
Date 2012-03-15 08:19 +0000
Organization A noiseless patient Spider
Message-ID <20120315081950.GD4808@yahoo.fr> (permalink)
References <55e8c993-a9ca-4e30-a85c-18430f2eb025@db5g2000vbb.googlegroups.com> <86pqcfbvud.fsf@gray.siamics.net> <0844dc91-9a86-4c72-be7f-39fd85fc1f0d@t16g2000yqt.googlegroups.com> <jjqg9u$c3i$1@speranza.aioe.org> <jjrkjr$gia$1@dont-email.me>

Show all headers | View raw


2012-03-15 03:36:43 +0100, Aragorn:
> On Wednesday 14 March 2012 17:17, Janis Papanagnou conveyed the 
> following to comp.unix.shell...
> 
> > Am 14.03.2012 16:54, schrieb Paul Branon:
> >>
> >> How do you create a file with no name?
> > 
> > I think the point was to have a file in the file system without any
> > directory entry pointing to the file. Let a process write to a file,
> > (which is done through a file handle), and while it's written delete
> > it from the diretory. The file is still growing if the process still
> > writes to it but inaccessible by name otherwise.
> 
> And _that_ is exactly what Adobe's Flashplayer plugin does.  Before, it 
> simply opened the file in "/tmp" (or "~/tmp") and would only delete the 
> filename when you closed the Flashplayer or navigated to another video - 
> e.g. on YouTube.  But now it opens the file (in "/tmp") and immediately 
> deletes the filename again from the directory.
[...]

No need to look so far.

That's what the *shell* does in

cmd << EOF
bar
EOF

or

cmd <<< 'string'

~$ lsof -c lsof -ad 0 <<< x
COMMAND  PID     USER   FD   TYPE DEVICE SIZE/OFF   NODE NAME
lsof    8993 chazelas    0r   REG  253,6        2 792578 /var/tmp/zshlpZ9cu (deleted)

-- 
Stephane

Back to comp.unix.shell | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

empty file is simply an inode with sort of null pointers Andre Aitken <andre.aitken.a@gmail.com> - 2012-03-13 21:46 -0700
  Re: empty file is simply an inode with sort of null pointers Ivan Shmakov <oneingray@gmail.com> - 2012-03-14 12:22 +0700
    Re: empty file is simply an inode with sort of null pointers Paul Branon <paulbranon@googlemail.com> - 2012-03-14 08:54 -0700
      Re: empty file is simply an inode with sort of null pointers Janis Papanagnou <janis_papanagnou@hotmail.com> - 2012-03-14 17:17 +0100
        Re: empty file is simply an inode with sort of null pointers Aragorn <stryder@telenet.be.invalid> - 2012-03-15 03:36 +0100
          Re: empty file is simply an inode with sort of null pointers Stephane Chazelas <stephane_chazelas@yahoo.fr> - 2012-03-15 08:19 +0000
          Re: empty file is simply an inode with sort of null pointers Barry Margolin <barmar@alum.mit.edu> - 2012-03-15 10:59 -0400
            Re: empty file is simply an inode with sort of null pointers Aragorn <stryder@telenet.be.invalid> - 2012-03-19 07:22 +0100
          Re: empty file is simply an inode with sort of null pointers William Ahern <william@wilbur.25thandClement.com> - 2012-03-18 23:57 -0700
      "a file which at this time has no name" Ivan Shmakov <oneingray@gmail.com> - 2012-03-14 23:48 +0700
        Re: lseek(2) operators in shells Stephane Chazelas <stephane_chazelas@yahoo.fr> - 2012-03-14 17:11 +0000
          Re: lseek(2) operators in shells Casper H.S. Dik <Casper.Dik@OrSPaMcle.COM> - 2012-03-14 17:44 +0000
          Re: lseek(2) operators in shells Kaz Kylheku <kaz@kylheku.com> - 2012-03-14 18:10 +0000
            Re: lseek(2) operators in shells "Chris F.A. Johnson" <cfajohnson@gmail.com> - 2012-03-14 15:20 -0400
              Re: lseek(2) operators in shells Kaz Kylheku <kaz@kylheku.com> - 2012-03-14 19:46 +0000
                Re: lseek(2) operators in shells Janis Papanagnou <janis_papanagnou@hotmail.com> - 2012-03-15 00:14 +0100
                Re: lseek(2) operators in shells "Mirko K." <mirkok.lists@googlemail.com> - 2012-03-15 00:45 +0100
                Re: lseek(2) operators in shells Janis Papanagnou <janis_papanagnou@hotmail.com> - 2012-03-15 01:11 +0100
                Re: lseek(2) operators in shells Kaz Kylheku <kaz@kylheku.com> - 2012-03-15 00:27 +0000
                Re: lseek(2) operators in shells "Mirko K." <mirkok.lists@googlemail.com> - 2012-03-15 01:35 +0100
                Re: lseek(2) operators in shells Kaz Kylheku <kaz@kylheku.com> - 2012-03-15 00:42 +0000
                Re: lseek(2) operators in shells Headless /body <devnull@NotReallyAn.example.com> - 2012-03-14 22:49 -0400
                Re: lseek(2) operators in shells Stephane Chazelas <stephane_chazelas@yahoo.fr> - 2012-03-15 08:17 +0000
                Re: lseek(2) operators in shells Janis Papanagnou <janis_papanagnou@hotmail.com> - 2012-03-15 09:32 +0100
                Re: lseek(2) operators in shells Janis Papanagnou <janis_papanagnou@hotmail.com> - 2012-03-15 09:26 +0100
              Re: lseek(2) operators in shells Barry Margolin <barmar@alum.mit.edu> - 2012-03-14 15:48 -0400
                Re: lseek(2) operators in shells Headless /body <devnull@NotReallyAn.example.com> - 2012-03-14 22:58 -0400
            Re: lseek(2) operators in shells Ben Bacarisse <ben.usenet@bsb.me.uk> - 2012-03-14 20:28 +0000
              Re: lseek(2) operators in shells Guillaume Dargaud <use_the_contact_form@www.gdargaud.net> - 2012-03-15 08:43 +0100
                dereferencing links to man(1) pages Ivan Shmakov <oneingray@gmail.com> - 2012-03-15 15:03 +0700
                Re: dereferencing links to man(1) pages Stephane Chazelas <stephane_chazelas@yahoo.fr> - 2012-03-15 13:36 +0000
                Re: dereferencing links to man(1) pages Dan Espen <despen@verizon.net> - 2012-03-15 10:02 -0400
                Re: lseek(2) operators in shells Ben Bacarisse <ben.usenet@bsb.me.uk> - 2012-03-15 12:40 +0000
              Re: lseek(2) operators in shells Barry Margolin <barmar@alum.mit.edu> - 2012-03-15 10:56 -0400
                Re: lseek(2) operators in shells Ben Bacarisse <ben.usenet@bsb.me.uk> - 2012-03-15 15:13 +0000
                Re: lseek(2) operators in shells Barry Margolin <barmar@alum.mit.edu> - 2012-03-15 13:09 -0400
                Re: lseek(2) operators in shells Ben Bacarisse <ben.usenet@bsb.me.uk> - 2012-03-15 17:29 +0000
        Re: "a file which at this time has no name" Paul Branon <paulbranon@googlemail.com> - 2012-03-15 05:27 -0700
          Re: "a file which at this time has no name" Ivan Shmakov <oneingray@gmail.com> - 2012-03-15 20:46 +0700
            Re: "a file which at this time has no name" "Mirko K." <mirkok.lists@googlemail.com> - 2012-03-15 22:29 +0100
              Re: "a file which at this time has no name" William Ahern <william@wilbur.25thandClement.com> - 2012-03-15 17:55 -0700
              Re: "a file which at this time has no name" pacman@kosh.dhis.org (Alan Curry) - 2012-03-16 01:09 +0000
                Re: "a file which at this time has no name" Ivan Shmakov <oneingray@gmail.com> - 2012-03-16 09:33 +0700
                Re: "a file which at this time has no name" pacman@kosh.dhis.org (Alan Curry) - 2012-03-16 09:51 +0000
                Re: "a file which at this time has no name" "Mirko K." <mirkok.lists@googlemail.com> - 2012-03-16 18:27 +0100
              Re: "a file which at this time has no name" Casper H.S. Dik <Casper.Dik@OrSPaMcle.COM> - 2012-03-16 14:39 +0000
  Re: empty file is simply an inode with sort of null pointers Kaz Kylheku <kaz@kylheku.com> - 2012-03-14 17:30 +0000

csiph-web