Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!news.bbnplanet.com!cpk-news-hub1.bbnplanet.com!EU.net!sun4nl!fwi.uva.nl!not-for-mail From: casper@fwi.uva.nl (Casper H.S. Dik) Newsgroups: comp.unix.solaris,comp.unix.bsd.misc Subject: Re: /proc (was Solaris 2.6) I guess we should talk. Supersedes: <cancel.casper.32a7e3b7@mail.fwi.uva.nl> Date: 6 Dec 1996 10:13:28 +0100 Organization: Sun Microsystems, Netherlands Lines: 25 Distribution: world Message-ID: <casper.32a7e3b7@mail.fwi.uva.nl> NNTP-Posting-Host: mail.fwi.uva.nl Xref: euryale.cc.adfa.oz.au comp.unix.solaris:91555 comp.unix.bsd.misc:1689 Richard Campbell <ric@ny.ubs.com> writes: >One feature I'd like to see is to have core files produced under >the /proc tree somewhere, presumably backed by tmp/swap space. >It's a drag to have large core files produced by the kernel >in the current directory when that directory is NFS/AFS/DFS >mounted. There's no real need to have those MBs of core data written >across the network; I'd rather they were stored locally allong with >other proc info. As soon as a process core dumps, it's gone. So there's no /proc stuff available for it anymore. I don't see how you can change the current core dumping semantics easily. (I mean, some people don't have the space locally to have a large core file, but do have such space over the network) Casper -- Casper Dik - Sun Microsystems - via my guest account at the University of Amsterdam. My work e-mail address is: Casper.Dik@Holland.Sun.COM Statements on Sun products included here are not gospel and may be fiction rather than truth.