2010/1/19 Mircea Vutcovici <[email protected]>: > 2010/1/19 Alex 'CAVE' Cernat <[email protected]>: >> >>> [wo...@wolfy tmp]$ mkfifo xulescu >>> [[wo...@wolfy tmp]$ touch yuleana >>> [wo...@wolfy tmp]$ ll x* y* >>> prw-rw-r-- 1 wolfy wolfy 0 2010-01-19 10:09 xulescu >>> -rw-rw-r-- 1 wolfy wolfy 0 2010-01-19 10:10 yuleana >>> [wo...@wolfy tmp]$ tar cf arhiva.tar xulescu yuleana >>> [wo...@wolfy tmp]$ tar tvf arhiva.tar >>> prw-rw-r-- wolfy/wolfy 0 2010-01-19 10:09 xulescu >>> -rw-rw-r-- wolfy/wolfy 0 2010-01-19 10:10 yuleana >>> [wo...@wolfy tmp]$ tar --version >>> tar (GNU tar) 1.20 >>> >> tare mi-e ca se referea la continutul socketilor si al pipelor pentru ca >> altfel intrebarea nu avea rost, tar-ul oricum arhiveaza by default >> fisierul pipe sau fisierul socket (adicatelea doar inode-ul respectiv, >> nu si ce se afla in socket sau in pipe la momentul respectiv) >> > > Ma refeream la fisierul special, nu la continut: > m...@server:~$ tar cf - /var/run/dbus/system_bus_socket|tar tvf - > tar: Removing leading `/' from member names > tar: /var/run/dbus/system_bus_socket: socket ignored > m...@server:~$ echo /var/run/dbus/system_bus_socket|cpio --create|cpio --list > 1 block > /var/run/dbus/system_bus_socket > 1 block > m...@server:~$ ls -l /var/run/dbus/system_bus_socket > srwxrwxrwx 1 root root 0 2009-09-05 17:24 /var/run/dbus/system_bus_socket
named pipes da, unix sockets nu. Recunosc ca nu realizez suficient de bine diferenta in afara de litera de la ls :P Mai studiez problema si revin cu amanunte. -- Petre "don't thread on me" Ratiu _______________________________________________ RLUG mailing list [email protected] http://lists.lug.ro/mailman/listinfo/rlug
