소스 검색

klish-2.2.3

Serj Kalichev 2 년 전
부모
커밋
e39cfa2ca0
2개의 변경된 파일7개의 추가작업 그리고 2개의 파일을 삭제
  1. 1 1
      configure.ac
  2. 6 1
      doc/klish.md

+ 1 - 1
configure.ac

@@ -2,7 +2,7 @@
 # Process this file with autoconf to produce a configure script.
 m4_define([MAJOR_VERSION], 2)
 m4_define([MINOR_VERSION], 2)
-m4_define([MICRO_VERSION], 2)
+m4_define([MICRO_VERSION], 3)
 
 AC_PREREQ(2.59)
 AC_INIT([klish],

+ 6 - 1
doc/klish.md

@@ -1682,7 +1682,7 @@ $ make LDFLAGS+="-all-static"
 
 The LDFLAGS is global so shared libraries can't be build and building of shared libraries must be disabled.
 
-## Leak of dlopen()
+### Leak of dlopen()
 
 If target system doesn't support dlopen() then configure script will configure building process to don't use dlopen() (and other dl functions) but link to plugin's shared objects.
 
@@ -1693,6 +1693,11 @@ $ ac_cv_header_dlfcn_h=no ./configure --prefix=/usr --with-lua --disable-shared
 $ make LDFLAGS+="-all-static"
 ```
 
+### Glibc's NSS
+
+The standard glibc uses dlopen() to implement getpwnam()-like and some other functions. The cause is NSS engine. It allows to use different backends (like LDAP, NIS. etc) for name resolution. The implementations of backends are in the separate shared objects. So NSS-depended functions can't be statically linked in common case (note glibc can be build with special option to enable NSS static linkage).
+
+The klish configure script has a special option `--disable-nss` to don't use standard NSS functions. The functions like getpwnam() will simulate standard behaviour. In this mode functions can't resolve user/group names but take only the numbers like '0' for root. But klish can be build fully statically in this mode. Implemented since klish-2.2.3.