In article <glp3rc$23p...@sf1.isc.org>, Jan Arild =?iso-8859-1?Q?Lindstr=F8m?= <j...@telenor.net> wrote: > >Hi, > >ah, of course. I did not think about it as a Solaris bug. > >I patched BIND 9.6.0-P1 os.c code so it first checks for the diretory >before it tries the fast approach of just running mkdir. And that of >course works fine. > >But, since I do not want to run a self-patch BIND in production, I will >instead run with pid-file "/var/run/named/named/named.pid" and be happy >with that.
Just wondering. Since /var/run is a swap (memory) based file system, do you have to recreate those directories on each reboot? >Thanks >Jan Arild Lindstr > > >At 15:35 27/01/2009, Mark Andrews wrote: > >>Looking at the publically available parts of SunSolve there are at least >>bug reports about it. >> >>Requires Support Contract tmp_mkdir()/xmemfs_mkdir() inconsistent with oth= >er xxxfs_mkdir() functions. | Open in a new window >>bug 6253984 >>http://sunsolve.sun.com/search/document.do?assetkey=3D1-1-6253984-1 - Sep = >10, 2007 >> = > >>Requires Support Contract tmp_mkdir()/xmemfs_mkdir() inconsistent with oth= >er xxxfs_mkdir() functions. | Open in a new window >>bug 2152581 >>http://sunsolve.sun.com/search/document.do?assetkey=3D1-1-2152581-1 - Sep = >10, 2007 = > >>I don't have a copy of the POSIX standard that covers mkdir(2) to >>see what it has to say about it. Historically however EACCES on >>search failure, EEXIST if the file/directory exists, then EACCES on >>parent directory write permissions was the error determination order. >> >>Mark >>-- = > >>Mark Andrews, ISC >>1 Seymour St., Dundas Valley, NSW 2117, Australia >>PHONE: +61 2 9871 4742 INTERNET: mark_andr...@isc.org > >_______________________________________________ >bind-users mailing list >bind-users@lists.isc.org >https://lists.isc.org/mailman/listinfo/bind-users -- Tom Schulz sch...@adi.com _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
