search for: pathconf

Does win32 have pathconf() and _PC_NAME_MAX? I ask for ogg123 -- it uses "NAME_MAX" right now (already been mentioned on this list a few times), which does not exist everywhere. I've proposed changing it to use the pathconf() function, but I don't know if win32 has this or not (I don't have, or want...

...n really in question is getopt_long(), because getopt() is standard POSIX. See http://www.xiph.org/archives/vorbis-dev/200012/0359.html for a discussion of this issue. 2. Also, NAME_MAX is used in ogg123/ao_interface.c -- this constant is not portable (doesn't exist in Solaris, for example). pathconf() should really be used instead. POSIX 1003.1a, section 2.9.5, table 2-5 contains [NAME_MAX] and the related text states: ----- A definition of one of the values from Table 2-5 shall be omitted from the <limits.h> on specific implementations where the corresponding value is equal to or grea...

I had a failure over the weekend of my ext3 filesystems. Hardware: Dell 2550 (dual PIII 1 Ghz, 1GB ram, Acenic GigE card) Software: linux-2.4.14 ext3-2.4-0.9.15-2414 Trond's NFS patches (pathconf, tune,read,rpc_blk) The filesystem is RAID0 using LVM (1.0.1-rc4). The disks are connected using fiber channel (qlogic 2200, qlax00-4.27beta). I was generating high load on my nfs server that is using ext3 filesystems. I started to get the following error: EXT3-fs error (device lvm(58,6)): e...

...== NULL) #else /* NGROUPS_MAX */ if((groups = (gid_t *)malloc(sizeof(gid_t)*ngroups)) == NULL) #endif /* NGROUPS_MAX */ As Donald Lewine's POSIX book says: "The values returned by these functions should be thought of as minimum guarantees. ... The values returned by sysconf() and pathconf() are not suitable for allocating memory." Running samba on Linux only above-showed source/smbd/password.c seems to be a problem since the other NGROUPS_MAX occurences only matter when things like a sane initgroups are missing. Suggestions etc. ? Sven

...gt; Thanks you. > > > If /mnt/DAT resizes on ZFS, then "vfs objects = zfsacl" must be set. > Hmm... looks like an autocorrect fail. If /mnt/DAT is a zpool, then you _must_ set "zfsacl". Attempts to set a POSIX1e ACL will fail with EINVAL. Typically in FreeBSD we use pathconf(2) to discover the ACL branding for the underlying filesystem, and then branding-aware syscalls. These are the sorts of os-specific nuances that we try to address through VFS modules. In this case, vfs_zfsacl will do mostly the right thing.

...create mkdir symlink mknod 20009850 4% 6065319 1% 3757720 0% 1557 0% 0 0% 0 0% remove rmdir rename link readdir readdirplus 6378134 1% 281 0% 2602358 0% 555097 0% 53126619 12% 15615402 3% fsstat fsinfo pathconf commit 113256 0% 26152 0% 0 0% 4026151 0% and this is the same on one of the new ones: amateo_adm at myotis31:~$ nfsstat Server rpc stats: calls badcalls badclnt badauth xdrcall 0 0 0 0 0 Client rpc stats: calls retrans...

...0% 87 0% read write create mkdir symlink mknod 153630 5% 36875 1% 709 0% 26 0% 0 0% 0 0% remove rmdir rename link readdir readdirplus 6729 0% 144 0% 350 0% 0 0% 1879 0% 165178 5% fsstat fsinfo pathconf commit 6002 0% 8 0% 0 0% 16872 0% thank you for your help in advance! Klaus ____________________________________________________ Aufnehmen, abschicken, nah sein - So einfach ist WEB.DE Video-Mail: http://freemail.web.de/?mc=021200

...l: NAME_MAX As has been pointed out on this list and the vorbis-list, NAME_MAX is not portable and should not be used. PATHNAME_MAX should be used instead. See http://www.xiph.org/archives/vorbis-dev/200101/0380.html and http://www.xiph.org/archives/vorbis/200012/0183.html. The short version is: pathconf() should be used instead of NAME_MAX. -- "buffer.c", line 57: warning: assignment type mismatch: volatile pointer to struct chunk_s {long len, array[4096] of char data} Self explanitory. -- In Solaris (and others), connect/socket are in libsocket.a, and gethostbyname is in libnsl.a. Ne...

...4% 0 0% read write create mkdir symlink mknod 649838729 19% 502171416 14% 29188492 0% 301741 0% 0 0% 0 0% remove rmdir rename link readdir readdirplus 54138192 1% 19903 0% 30702957 0% 27796623 0% 1294453 0% 84457031 2% fsstat fsinfo pathconf commit 48529 0% 31463 0% 0 0% 11339977 0% Output of iostat: Linux 2.4.27-3-686-smp (data.clm.net4all.ch) 21. 07. 06 cpu-moy: %user %nice %sys %iowait %idle 0,16 0,00 1,65 0,00 98,19 Device: tps Blk_lus/s Blk_?crits/s Blk_lus Blk_?cr...

I am the maintainer of GDM, and I am noticing that GDM has a problem when running on a ZFS filesystem, as with Indiana. When GDM (the GNOME Display Manager) starts the login GUI, it runs the following commands on Solaris: /usr/bin/setfacl -m user:gdm:rwx,mask:rwx /dev/audio /usr/bin/setfacl -m user:gdm:rwx,mask:rwx /dev/audioctl It does this because the login GUI programs are run as the

Hello all, First off, i''m talking about a SXDE build 89. Sorry if that was discussed here before, but i did not find anything related on the archives, and i think is a "weird" issue... If i try to remove a specific file, i got: # rm file1 rm: file1: No such file or directory # rm -rf dir2 rm: Unable to remove directory dir2: Directory not empty Take a look: ------- cut

https://bugzilla.samba.org/show_bug.cgi?id=8001 Summary: buffer overflow in recv_file_entry (maxpathlen doesn't works) Product: rsync Version: 3.0.8 Platform: All OS/Version: FreeBSD Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org

On 9/16/20 2:27 AM, Andrew Walker wrote: > > > On Tue, Sep 15, 2020 at 2:58 PM Budi Janto via samba > <samba at lists.samba.org <mailto:samba at lists.samba.org>> wrote: > > Hi, > > For 3 days uptime serve about 40 client Windows workstation with traffic > average 50 Mbps - 80 Mbps (Video streaming) running on FreeBSD system > with 16

I asked about this ability a few weeks ago and the reply was basically that folks would be interested in seeing it happen. Well, the client insisted, so I've put together a hack that accomplishes it. The basic design requirement was that users would not see files/directories that they did not have at least read access to. This request came about because we were migrating from a Novell server,

...setnetgrent... no > checking for getnetgrent... no > checking for endnetgrent... no > checking for initgroups... no > checking for select... no > checking for poll... no > checking for rdchk... no > checking for getgrnam... no > checking for getgrent... no > checking for pathconf... no > checking for realpath... no > checking for setpriv... no > checking for setgidx... no > checking for setuidx... no > checking for setgroups... no > checking for sysconf... no > checking for mktime... no > checking for rename... no > checking for ftruncate... no &g...

...g for sigblock... no checking for sigaction... yes checking for innetgr... yes checking for setnetgrent... yes checking for getnetgrent... yes checking for endnetgrent... yes checking for initgroups... yes checking for select... yes checking for rdchk... no checking for getgrnam... yes checking for pathconf... yes checking for setuidx... no checking for setgroups... yes checking for mktime... yes checking for rename... yes checking for ftruncate... yes checking for stat64... yes checking for fstat64... yes checking for lstat64... yes checking for fopen64... yes checking for atexit... yes checking for...

...cking for innetgr... yes checking for setnetgrent... yes checking for getnetgrent... yes checking for endnetgrent... yes checking for initgroups... yes checking for select... yes checking for poll... yes checking for rdchk... no checking for getgrnam... yes checking for getgrent... yes checking for pathconf... yes checking for setpriv... no checking for setgidx... no checking for setuidx... no checking for setgroups... yes checking for sysconf... yes checking for mktime... yes checking for rename... yes checking for ftruncate... yes checking for stat64... no checking for fstat64... no checking for lst...

..... no checking for innetgr... no checking for setnetgrent... no checking for getnetgrent... no checking for endnetgrent... no checking for initgroups... no checking for select... no checking for poll... no checking for rdchk... no checking for getgrnam... no checking for getgrent... no checking for pathconf... no checking for realpath... no checking for setpriv... no checking for setgidx... no checking for setuidx... no checking for setgroups... no checking for sysconf... no checking for mktime... no checking for rename... no checking for ftruncate... no checking for stat64... no checking for fstat64....

..... no checking for innetgr... no checking for setnetgrent... no checking for getnetgrent... no checking for endnetgrent... no checking for initgroups... no checking for select... no checking for poll... no checking for rdchk... no checking for getgrnam... no checking for getgrent... no checking for pathconf... no checking for realpath... no checking for setpriv... no checking for setgidx... no checking for setuidx... no checking for setgroups... no checking for sysconf... no checking for mktime... no checking for rename... no checking for ftruncate... no checking for stat64... no checking for fstat64....

...netgrent configure:5534: checking for endnetgrent configure:5589: checking for initgroups configure:5589: checking for select configure:5589: checking for poll configure:5589: checking for rdchk configure:5589: checking for getgrnam configure:5589: checking for getgrent configure:5589: checking for pathconf configure:5589: checking for realpath configure:5644: checking for setpriv configure:5644: checking for setgidx configure:5644: checking for setuidx configure:5644: checking for setgroups configure:5644: checking for sysconf configure:5644: checking for mktime configure:5644: checking for rename co...