search for: s_isvtx

...;, {st_mode=S_IFDIR|0755, st_size=1024, ...}) = 0 stat64("/proc", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0 stat64("/", {st_mode=S_IFDIR|0755, st_size=1024, ...}) = 0 stat64("/sys", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0 stat64("/dev", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=3760, ...}) = 0 stat64("/proc", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0 stat64("/sys/fs/cgroup", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0 stat64("/boot", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat64("/usr/local/config", {st_mode=...

.../usr/local/bin/smbsh", ["smbsh"], [/* 37 vars */]) = 0 brk(0) = 0x8075e5c open("/etc/ld.so.preload", O_RDONLY) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY) = 5 fstat(5, {st_mode=S_IFDIR|S_ISUID|S_ISVTX|0371, st_size=0, ...}) = 0 mmap(0, 18920, PROT_READ, MAP_PRIVATE, 5, 0) = 0x40014000 close(5) = 0 open("/lib/libdl.so.2", O_RDONLY) = 5 fstat(5, {st_mode=0, st_size=0, ...}) = 0 read(5, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3"..., 4096) = 4096 m...

Hi all, I installed glusterfs (version 3.1.3) with zfs-fuse (0.6.9) as the underlying filesystem. After renaming a file, I found the file duplicated. Following is my test scenario. root at ubuntu:/# zpool create tank /dev/sdb root at ubuntu:/# gluster volume create test-volume ubuntu:/tank/exp1 ubuntu:/exp2 root at ubuntu:/# gluster volume start test-volume root at ubuntu:/# mount -t glusterfs

...id some research and found that ALLPERMS is not in POSIX-96 or POSIX-01. Therefore, I don't think it is wise to use it in rsync, unless one were to write a full-bore configure test, and define it if it is not present. The POSIX-01 description of chmod() says that it changes S_ISUID, S_ISGID, S_ISVTX, and the file permission bits. My feeling is that it would be ok to use a mask of those 3 macros with 0777; any implementation that doesn't make the file permission bits the low-order 9 bits with their usual definition is insane. Actually, I think the original definition (below), is just f...

...f-exclude -u rsync-2.5.5/rsync.h rsync/rsync.h --- rsync-2.5.5/rsync.h Mon Mar 25 02:29:43 2002 +++ rsync/rsync.h Fri Feb 7 10:02:09 2003 @@ -488,9 +488,53 @@ #define STDERR_FILENO 2 #endif +#ifndef S_ISUID +#define S_ISUID 04000 +#endif +#ifndef S_ISGID +#define S_ISGID 02000 +#endif +#ifndef S_ISVTX +#define S_ISVTX 01000 +#endif +#ifndef S_IRWXU +#define S_IRWXU 00700 +#endif +#ifndef S_IRUSR +#define S_IRUSR 00400 +#endif #ifndef S_IWUSR -#define S_IWUSR 0200 +#define S_IWUSR 00200 +#endif +#ifndef S_IXUSR +#define S_IXUSR 00100 +#endif +#ifndef S_IRWXG +#define S_IRWXG 00070 +#endif +#ifnd...

Hello, i'm using rsync 2.6.0 for daily-syncing some remote AIX 5.2 machine to a local linux (RH 7.3) with using the --link-dest option for saving space on incremental backups. Even if there are no changes on the AIX machine, all files are newly transferred on every new sync. My test scenario (actisi=remote aix machine, actisa=local linux machine): =====> Initial rsync [mma@actisa

...{st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat("/proc", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0 stat("/sys", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0 stat("/var/run", {st_mode=S_IFDIR|0755, st_size=400, ...}) = 0 stat("/var/lock", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=40, ...}) = 0 stat("/dev", {st_mode=S_IFDIR|0755, st_size=12820, ...}) = 0 stat("/dev/shm", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=40, ...}) = 0 stat("/dev/pts", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0 stat("/home/dovecot", {st_mode=S_IFDIR|...

...b/permstring.c newrsync/lib/permstring.c --- oldrsync/lib/permstring.c Tue Aug 27 11:05:47 2002 +++ newrsync/lib/permstring.c Tue Aug 27 15:45:34 2002 @@ -47,8 +47,10 @@ void permstring(char *perms, if (mode & S_ISGID) perms[6] = (mode & S_IXGRP) ? 's' : 'S'; +#ifdef S_ISVTX if (mode & S_ISVTX) perms[9] = (mode & S_IXOTH) ? 't' : 'T'; +#endif if (S_ISLNK(mode)) perms[0] = 'l'; if (S_ISDIR(mode)) perms[0] = 'd'; diff -urp --new-file oldrsync/rsync.h newrsync/rsync.h --- oldrsync/rsync.h Tue Aug 27 12:03:52 2002 +++ ne...

...b/permstring.c newrsync/lib/permstring.c --- oldrsync/lib/permstring.c Tue Aug 27 11:05:47 2002 +++ newrsync/lib/permstring.c Tue Aug 27 15:45:34 2002 @@ -47,8 +47,10 @@ void permstring(char *perms, if (mode & S_ISGID) perms[6] = (mode & S_IXGRP) ? 's' : 'S'; +#ifdef S_ISVTX if (mode & S_ISVTX) perms[9] = (mode & S_IXOTH) ? 't' : 'T'; +#endif if (S_ISLNK(mode)) perms[0] = 'l'; if (S_ISDIR(mode)) perms[0] = 'd'; diff -urp --new-file oldrsync/rsync.h newrsync/rsync.h --- oldrsync/rsync.h Tue Aug 27 12:03:52 2002 +++ ne...

...b/permstring.c newrsync/lib/permstring.c --- oldrsync/lib/permstring.c Tue Aug 27 11:05:47 2002 +++ newrsync/lib/permstring.c Tue Aug 27 15:45:34 2002 @@ -47,8 +47,10 @@ void permstring(char *perms, if (mode & S_ISGID) perms[6] = (mode & S_IXGRP) ? 's' : 'S'; +#ifdef S_ISVTX if (mode & S_ISVTX) perms[9] = (mode & S_IXOTH) ? 't' : 'T'; +#endif if (S_ISLNK(mode)) perms[0] = 'l'; if (S_ISDIR(mode)) perms[0] = 'd'; diff -urp --new-file oldrsync/rsync.h newrsync/rsync.h --- oldrsync/rsync.h Tue Aug 27 12:03:52 2002 +++ ne...

...b/permstring.c newrsync/lib/permstring.c --- oldrsync/lib/permstring.c Tue Aug 27 10:05:47 2002 +++ newrsync/lib/permstring.c Sun Nov 17 04:58:47 2002 @@ -47,8 +47,10 @@ void permstring(char *perms, if (mode & S_ISGID) perms[6] = (mode & S_IXGRP) ? 's' : 'S'; +#ifdef S_ISVTX if (mode & S_ISVTX) perms[9] = (mode & S_IXOTH) ? 't' : 'T'; +#endif if (S_ISLNK(mode)) perms[0] = 'l'; if (S_ISDIR(mode)) perms[0] = 'd'; diff -urp oldrsync/rsync.h newrsync/rsync.h --- oldrsync/rsync.h Sun Nov 17 05:00:06 2002 +++ newrsync/rsyn...

Hi all, I'm using a build of dovecot 1.2, and I'm seeing this: # ls -al 1235038385.M765212P13483.tch-mailstore1\,S\=3927\,W\=4017\:2\,S -rw------- 1 mail mail 3927 2009-02-19 10:13 1235038385.M765212P13483.tch-mailstore1,S=3927,W=4017:2,S (root at tch-mailstore1:/mailstore/mail/domain.net/i/ian/mail/.postini/cur) (2009-02-23 13:46:04) # sieve-test -c ../../../sieve/default.sieve

...emp dir and pass all the gunky options to mount. */ if (chdir(_PATH_TMP)) { - perror(program); + fprintf(stderr, "%s: Cannot access the %s directory.\n", + program, _PATH_TMP); exit(1); } #define TMP_MODE (S_IXUSR|S_IWUSR|S_IXGRP|S_IWGRP|S_IWOTH|S_IXOTH|S_ISVTX)

...rmissions 1777. Then use scp -rp dir user at otherhost: The resulting directory on the otherhost will have permissions of 0777 instead of 1777. From the security point of view this may considered a serious problem. Location of the problem: in scp.c the FILEMODEMASK does not include the sticky bit (S_ISVTX). -- Configure bugmail: https://bugzilla.mindrot.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

Hi everyone, We are trying to port our own windows application to SUSE linux.Our application uses SetFilePerm() api defined in commondll.dll.We would like to know whether there is a linux equivalent of windows commondll.dll in wine... If not then what could be the possible alternative to make this api function exactly as it does in windows. Waiting for an early reply, Thanks and Regards,

Hello, I have two little problems with samba: 1st. Samba is not setting the sticky bit anymore !!! I have a share that look like this: [publico] comment = Arquivos publicos path = /home/publicos public = yes writable = yes force directory mode = 1777 create mask = 0664 With samba 1.9.x it was ok, the directories was being created with the correct permission (drwxrwxrwt), but since I

...} +/* copy of check_sticky in fs/namei.c() +* It''s inline, so penalty for filesystems that don''t use sticky bit is +* minimal. +*/ +static inline int btrfs_check_sticky(struct inode *dir, struct inode *inode) +{ + uid_t fsuid = current_fsuid(); + + if (!(dir->i_mode & S_ISVTX)) + return 0; + if (inode->i_uid == fsuid) + return 0; + if (dir->i_uid == fsuid) + return 0; + return !capable(CAP_FOWNER); +} + +/* copy of may_delete in fs/namei.c() + * Check whether we can remove a link victim from directory dir, check + * whether the type of victim is right. + *...

...S_ISGID) ? + putchar(STAT_ISSET(st->st_mode, S_IXGRP) ? 'x' : '-') : + putchar('S'); + + putchar(STAT_ISSET(st->st_mode, S_IROTH) ? 'r' : '-'); + putchar(STAT_ISSET(st->st_mode, S_IWOTH) ? 'w' : '-'); + + !STAT_ISSET(st->st_mode, S_ISVTX) ? + putchar(STAT_ISSET(st->st_mode, S_IXOTH) ? 'x' : '-') : + putchar(S_ISDIR(st->st_mode) ? 't' : 'T'); + + if (S_ISCHR(st->st_mode) || S_ISBLK(st->st_mode)) { + rc = asprintf(&fmt," %%%dju %%%dju %%%dju %%%du,%%%du %%s", +...

...t_mode, S_IXGRP) ? "x" : "-") : + printf ("S"); + + printf ("%s%s", + STAT_ISSET(st->st_mode, S_IROTH) ? "r" : "-", + STAT_ISSET(st->st_mode, S_IWOTH) ? "w" : "-"); + + !STAT_ISSET(st->st_mode, S_ISVTX) ? + printf ("%s", STAT_ISSET(st->st_mode, S_IXOTH) ? "x" : "-") : + printf ("%s", S_ISDIR(st->st_mode) ? "t" : "T"); + + sz = snprintf(NULL, 0, " %%%dju %%%dju %%%dju", max_nlinks, max_uid, max_gid); + if ((fmt = malloc(...

Hi, I have run into an issue using puppet in an ldap environment and I am wondering if anyone else has run into the same issue. A number of the puppet clients in my testing environment are failing to apply new configurations because the puppet client is getting an ldap error. Currently, I am attempting to push a new bash_profile to my home directory and then set my username/group to then own the