Re: [OpenAFS] bos: can't open cell database
Michal Gutowski wrote: hi, my problem is, (on FC5) when i do /usr/afs/bin/ ./bosserver -noauth it makes me usr/local/etc/openafs/server/Thiscell and there is no CellServDB maybe it's no aproblem so i make next step ./usr/afs/bin/ ./bos setcellname open.tech.tc tech.tc -noauth bos: can't open cell database (/usr/local/etc/openafs) This error means that the directory /usr/local/etc/openafs does not exist. You're sure it's there ? and i dont know what's wrong please help Christof ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] bos: can't open cell database
Christof Hanke napisał(a): Michal Gutowski wrote: hi, my problem is, (on FC5) when i do /usr/afs/bin/ ./bosserver -noauth it makes me usr/local/etc/openafs/server/Thiscell and there is no CellServDB maybe it's no aproblem so i make next step ./usr/afs/bin/ ./bos setcellname open.tech.tc tech.tc -noauth bos: can't open cell database (/usr/local/etc/openafs) This error means that the directory /usr/local/etc/openafs does not exist. You're sure it's there ? and i dont know what's wrong please help Christof Yes, I'm sure for 100% /usr/local/etc/openafs there're two symbolic links one for ThisCell second for CellServDB and they show to usr/local/etc/openafs/server/ Michal -- Slodkie jest zycie bandziora. Zobacz http://link.interia.pl/f19e5 ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] Question: discontinuing support for Solaris 2.6
On Sat, 13 Jan 2007, Derrick J Brashear wrote: I think at this point 2 people have asked about pre 2.6 recently, one 2.4 and one 2.5.1, and they can use old versions. Is anyone else? I am kind of wondering if we should knox 2.6 and 2.7 too.. http://www.sun.com/service/eosl/solaris/solaris_vintage_eol_5.2005.xml Solaris 2.6 is end of life as of 07/23/06 Solaris 2.7 is end of life as of 08/15/08 (2.7 entered in the last phase before retirement as of 08/15/05 ) I am pretty sure it doesnt kill a lot of messy ifdefs, except maybe some of the threaded code where you can use pthread instead of sun thread support. IIRC pthread wasn't fully implemented until solaris 8.. but maybe they backported it to the older versions. I don't really know. I am just thinking pretty much everyone was migrating off 7 and 8 right now, but I could be wrong. -- Sean O'Malley, Information Technologist Michigan State University - ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] Question: discontinuing support for Solaris 2.6
Sean O'Malley [EMAIL PROTECTED] writes: On Sat, 13 Jan 2007, Derrick J Brashear wrote: I think at this point 2 people have asked about pre 2.6 recently, one 2.4 and one 2.5.1, and they can use old versions. Is anyone else? I am kind of wondering if we should knox 2.6 and 2.7 too.. http://www.sun.com/service/eosl/solaris/solaris_vintage_eol_5.2005.xml Solaris 2.6 is end of life as of 07/23/06 Solaris 2.7 is end of life as of 08/15/08 (2.7 entered in the last phase before retirement as of 08/15/05 ) I am pretty sure it doesnt kill a lot of messy ifdefs, except maybe some of the threaded code where you can use pthread instead of sun thread support. IIRC pthread wasn't fully implemented until solaris 8.. but maybe they backported it to the older versions. I don't really know. I am just thinking pretty much everyone was migrating off 7 and 8 right now, but I could be wrong. Stanford doesn't really care at this point about anything prior to Solaris 8, but we do care a great deal about Solaris 8 and probably will for some time. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] Question: discontinuing support for Solaris 2.6
Russ Allbery [EMAIL PROTECTED] sent but probably didn't write: I am pretty sure it doesnt kill a lot of messy ifdefs, except maybe some of the threaded code where you can use pthread instead of sun thread support. IIRC pthread wasn't fully implemented until solaris 8.. but maybe they backported it to the older versions. I don't really know. ... I believe pthreads works fine in 2.6 -- I've heard people claim it worked better there than in later versions. (2.6 being the last 32-bit only system gave it a certain advantage in terms of stability...) I don't know of any reason to avoid it. The only solaris thread stuff I can find (in 1.5.12) is in lwp.c -- conditioned by the manifest USE_SOLARIS_THREADS which is apparently only turned on in the apparently defunct src/lwp/NTMake9x . I think you can pull all that old USE_SOLARIS_THREADS and not have any problems. There may be one other thing that matters - maybe. In a copy of openafs 1.2.10 for solaris 8 that I seem to have just had sitting around, there's one solaris threads call left -- thr_yield() calls. rx_pthread.h defined pthread_yield to be various things on different systems - this appears to be one area where pthread isn't really a standard, and thr_yield happened to be the winner on solaris. This is apparently still true today. I think this can be chalked up as a generic known OS issue with pthreads, not a specific problem with ancient solaris. -Marcus ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] bos: can't open cell database
Am Dienstag, 16. Januar 2007 20:20 schrieb ext Michal Gutowski: Yes, I'm sure for 100% /usr/local/etc/openafs there're two symbolic links one for ThisCell second for CellServDB and they show to usr/local/etc/openafs/server/ I guess they should point to /usr/..., not usr/... Bye... Dirk -- Dirk Heinrichs | Tel: +49 (0)162 234 3408 Configuration Manager | Fax: +49 (0)211 47068 111 Capgemini Deutschland | Mail: [EMAIL PROTECTED] Hambornerstraße 55 | Web: http://www.capgemini.com D-40472 Düsseldorf | ICQ#: 110037733 GPG Public Key C2E467BB | Keyserver: www.keyserver.net pgpL25VXSfxbT.pgp Description: PGP signature