Date: Thu, 12 May 2005 14:24:51 +0200 From: =?ISO-8859-1?Q?Herv=E9_Kergourlay?= <herve.kergourlay@atempo.com> To: Kris Kennaway <kris@obsecurity.org> Cc: questions@FreeBSD.org Subject: Re: FreeBSD 5.3 Message-ID: <42834B13.3020504@atempo.com> In-Reply-To: <20050512114342.GB58837@xor.obsecurity.org> References: <428306AF.1080108@atempo.com> <20050512114342.GB58837@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. --------------060200090506020703000708 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Kris Kennaway a écrit : >On Thu, May 12, 2005 at 09:33:03AM +0200, Herv? Kergourlay wrote: > > >>we are porting our product on FreeBSD 5.3 >> >>it's a backup product which is still running on FreeBSD 4.0 >> >>here's a list of questions after checking the documentation >> >>1) PAM >> >>it's working, the only problem is with the null password users, the >>answer is allways NO. the nullok doesn't seem active >>here is my PAM file >>auth required /usr/lib/pam_unix.so nullok >>account required /usr/lib/pam_unix.so nullok >> >> > >Which PAM file? 5.3 doesn't use a single /etc/pam.conf. > > it's our pam file in /etc/pam.d directory with the name registered in the pam_start first parameter > > >>5) where are generated the core files ? >> >>I change the kernel with the following command >>sysctl kern.corefile="/cores/%U/%P%N.core" >> >> > >Make sure those directories exist and are writable by the user. They >won't be created automatically. > > checked, I force the 777 mode on the /cores directory > > >>6) 2 last questions :-) >> >>what about files more than 4GB, do I need to use specific APIs as >>open64, stat64 or the current open and stat API are managing the big file ? >> >> > >No. > > so big file are managed without any pain. correct ? >Kris > > --------------060200090506020703000708--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42834B13.3020504>