Date: Tue, 7 Jul 1998 14:28:12 -0400 (EDT) From: "Ron G. Minnich" <rminnich@Sarnoff.COM> To: hackers@FreeBSD.ORG Subject: case in point for (A really hoopy idea for variant symlinks.) Message-ID: <Pine.SUN.3.91.980707142202.3601F-100000@terra>
next in thread | raw e-mail | index | archive | help
here ya go. This is working as of now. $ ls /proc c002 c012 c021 c030 c039 c048 c057 c003 c013 c022 c031 c040 c049 c059 c004 c014 c023 c032 c041 c050 c060 c005 c015 c024 c033 c042 c051 c061 c007 c016 c025 c034 c043 c052 localhost c008 c017 c026 c035 c044 c053 c009 c018 c027 c036 c045 c054 c010 c019 c028 c037 c046 c055 c011 c020 c029 c038 c047 c056 $ ls /proc/c00[23] /proc/c002: 1 183 207 6005 kcore pci 121 198 24 7 kmsg scsi 130 2 3 cmdline ksyms self 141 200 4 cpuinfo loadavg stat 14458 201 5 devices locks sys etc. etc. etc. $ cat /proc/c00[23]/1/status Name: init State: S (sleeping) Pid: 1 PPid: 0 Uid: 0 0 0 0 Gid: 0 0 0 0 etc. etc. etc. you get the point ... note that I don't have all the nodes. Some of them I don't care about it right now, one of them is out due to power outage which ate the disk. Didn't make a big difference. didn't hang my machine. Didn't (and can't) do much of anything to the system, since it's in my private name space and won't affect anyone else. If the remote servers or machines die, then my process will get an error when it tries to read that directory, but that's about it. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SUN.3.91.980707142202.3601F-100000>