Yes, indeed they are socket files. I had mistaken the 's' for symbolic
link, forgetting that indeed a Symbolic Link was 'l'
so I should be good to go.
|---------+---------------------------->
| | Rick Troth |
| | <[EMAIL PROTECTED]> |
| | Sent by: Linux on|
| | 390 Port |
| | <[EMAIL PROTECTED]|
| | IST.EDU> |
| | |
| | |
| | 03/20/2002 11:16 |
| | AM |
| | Please respond to|
| | Linux on 390 Port|
| | |
|---------+---------------------------->
>--------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: Authentication on Linux using PAM to a z/OS RACF server
|
>--------------------------------------------------------------------------------------------------------------|
> In my case I was copying the /var tree and it left out /var/run/printer
> and /var/run/.nscd_socket which are both symbolic links to elsewhere.
You sure they were sym-links and not "socket" files?
Sym-link should have an "l" in the far left of 'ls -l' output.
A named socket would have an "s" in the far left of the same listing.
Named sockets never get copied, from all the docs and refs I've seen.
Files which do get copied are: plain, directory (sort of),
char special, block special, symbolic link, and named pipe
(this last one not to be confused with named socket).
The two in question should be recreated automagically as needed.
