Yetixx
Yetixx
Server: nginx/1.28.0
System: Linux instance-rr9enuui 6.1.0-15-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.66-1 (2023-12-09) x86_64
User: www (1000)
PHP: 8.0.26
Disabled: passthru,exec,system,putenv,chroot,chgrp,chown,shell_exec,popen,proc_open,pcntl_exec,ini_alter,ini_restore,dl,openlog,syslog,readlink,symlink,popepassthru,pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,imap_open,apache_setenv
Upload Files
File: //usr/share/doc/bash-completion/README.Debian
bash-completion for Debian
--------------------------

 Completions are kept in /usr/share/bash-completion/completions.

 If a package installs its completion files under /etc/bash_completion.d/,
 bash-completion is still able to use them, but bash-completion itself does
 not install any files under that directory.

 If you are a package maintainer, you are encouraged to use
 dh_bash-completion(1), which will take care of installing third-party
 completions into the appropriate directory.

 -- David Paleino <dapal@debian.org>  Sun, 10 Apr 2011 15:33:19 +0200
 -- Gabriel F. T. Gomes <gabriel@inconstante.net.br>  Mon, 12 Feb 2018 21:46:42 -0200