Linux vps-61133.fhnet.fr 4.9.0-19-amd64 #1 SMP Debian 4.9.320-2 (2022-06-30) x86_64
Apache/2.4.25 (Debian)
Server IP : 93.113.207.21 & Your IP : 216.73.216.35
Domains :
Cant Read [ /etc/named.conf ]
User : www-data
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
usr /
include /
postgresql /
Delete
Unzip
Name
Size
Permission
Date
Action
internal
[ DIR ]
drwxr-xr-x
2024-03-12 14:15
libpq
[ DIR ]
drwxr-xr-x
2024-03-12 14:15
libpq-events.h
2.16
KB
-rw-r--r--
2021-11-12 08:56
libpq-fe.h
21.39
KB
-rw-r--r--
2021-11-12 08:56
pg_config.h
29.08
KB
-rw-r--r--
2021-11-12 08:56
pg_config_ext.h
323
B
-rw-r--r--
2021-11-12 08:56
pg_config_manual.h
11.38
KB
-rw-r--r--
2021-11-12 08:56
pg_config_os.h
1.03
KB
-rw-r--r--
2021-11-12 08:56
postgres_ext.h
2.1
KB
-rw-r--r--
2021-11-12 08:56
Save
Rename
/* src/include/port/linux.h */ /* * As of July 2007, all known versions of the Linux kernel will sometimes * return EIDRM for a shmctl() operation when EINVAL is correct (it happens * when the low-order 15 bits of the supplied shm ID match the slot number * assigned to a newer shmem segment). We deal with this by assuming that * EIDRM means EINVAL in PGSharedMemoryIsInUse(). This is reasonably safe * since in fact Linux has no excuse for ever returning EIDRM; it doesn't * track removed segments in a way that would allow distinguishing them from * private ones. But someday that code might get upgraded, and we'd have * to have a kernel version test here. */ #define HAVE_LINUX_EIDRM_BUG /* * Set the default wal_sync_method to fdatasync. With recent Linux versions, * xlogdefs.h's normal rules will prefer open_datasync, which (a) doesn't * perform better and (b) causes outright failures on ext4 data=journal * filesystems, because those don't support O_DIRECT. */ #define PLATFORM_DEFAULT_SYNC_METHOD SYNC_METHOD_FDATASYNC