Discuss August 2016

discuss@lists.centos.org

131 participants
135 discussions

None
by None 31 Aug '16

31 Aug '16

by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u7VHB9vm012262 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 31 Aug 2016 13:11:10 -0400 To: centos(a)centos.org References: <d059a28c-b866-5056-dda6-29e3077ca907(a)mit.edu> <8d10f9b1-0ed9-0217-ae0e-726acd1d9a87(a)gmail.com> From: Pat Haley <phaley(a)mit.edu> Message-ID: <8d59038f-3dbe-5bff-9673-fbada1d3f31c(a)mit.edu> Date: Wed, 31 Aug 2016 13:11:09 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <8d10f9b1-0ed9-0217-ae0e-726acd1d9a87(a)gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrFIsWRmVeSWpSXmKPExsUixG6nrrue/3i4wZSrFhbLzixgtpjy+x2T A5PHyrbJzB4XG5ewBjBFcdmkpOZklqUW6dslcGV8u2xY8Iq7oqd/OmMD4z7OLkYODgkBE4np a6K6GLk4hATamCSOdD1kgXA2Mkq8OLSFDcJZySQx5fg2xi5GTg5hAUeJFy+3s4HYIgKiEj2L X4HZQgK5EjNPHGQDmcosoC7RvpQVJMwmoCCx7tYZdhCbV8BKYvmPZ2A2i4CqxMTPH5lAbFGB CIlbqz4yQtQISpyc+YQFxOYUsJVYc/8QWA0zkH1n7m5mCFteYvvbOcwTGAVmIWmZhaRsFpKy BYzMqxhlU3KrdHMTM3OKU5N1i5MT8/JSi3SN9HIzS/RSU0o3MYKClFOSdwfjv7tehxgFOBiV eHgd3hwLF2JNLCuuzD3EKMnBpCTK2/IKKMSXlJ9SmZFYnBFfVJqTWnyIUYKDWUmEN4fneLgQ b0piZVVqUT5MSpqDRUmct2vGgXAhgfTEktTs1NSC1CKYrAwHh5IEbwYfUKNgUWp6akVaZk4J QpqJgxNkOA/Q8A8gNbzFBYm5xZnpEPlTjIpS4rx3eYESAiCJjNI8uF5wElFjP/SKURzoFWFe E5B2HmACgut+BTSYCWhwwZ3DIINLEhFSUg2MW8WcvRwnrJQpPGj6JO7Mjrup8+QnHfE2yHkh feS98eZoudO7Ti/PjZrzfUGd1fkVN6onGvKEzHjbKJ9wrrthyjrn+H/bG/OzzjAuDWaoKZjC x/Tlc9TrqfXiNZmXf+3s6Mk2LGQ3VEoRKrhyoCz4jM/zKU9+ZzlNP1jnIqd469Nuiw4NMdk9 SizFGYmGWsxFxYkAxP5Cf/0CAAA= Cc: Steve Postma <SPostma(a)ztechnet.com> Subject: Re: [CentOS] group write permissions not being respected X-BeenThere: centos(a)centos.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe: <https://lists.centos.org/mailman/options/centos>, <mailto:centos-request@centos.org?subject=unsubscribe> List-Archive: <http://lists.centos.org/pipermail/centos/> List-Post: <mailto:centos@centos.org> List-Help: <mailto:centos-request@centos.org?subject=help> List-Subscribe: <https://lists.centos.org/mailman/listinfo/centos>, <mailto:centos-request@centos.org?subject=subscribe> X-List-Received-Date: Wed, 31 Aug 2016 17:11:11 -0000 So far, those look the same client: [root@mseas FixOwn]# getfacl /gdata/bibliography/Work/GroupBib/trunk/ getfacl: Removing leading '/' from absolute path names # file: gdata/bibliography/Work/GroupBib/trunk/ # owner: phaley # group: mseasweb # flags: -s- user::rwx group::rwx other::r-x server: [root@mseas-data2 ~]# getfacl /gdata/bibliography/Work/GroupBib/trunk/ getfacl: Removing leading '/' from absolute path names # file: gdata/bibliography/Work/GroupBib/trunk/ # owner: phaley # group: mseasweb # flags: -s- user::rwx group::rwx other::r-x On 08/31/2016 12:50 PM, Gordon Messmer wrote: > On 08/30/2016 03:01 PM, Pat Haley wrote: >> the owner of a directory can still write to that directory but any >> other member of the associated group cannot, even though the >> directory clearly has group write permissions set > > > Use "getfacl" on both the client and server side to view the complete > permission set. What do those look like? > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley(a)mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301

1 0

CentOS 6 - logwatch report not in HTML format
by Arun Khan 31 Aug '16

31 Aug '16

CentOS 6 (amd64) up to date with latest security / bug fixes. The logwatch reports come in plain text even though the config states HTML. <begin /etc/logwatch/conf/logwatch.conf> mailer = "/usr/sbin/sendmail -t" TmpDir = /tmp MailFrom = logwatch(a)example.com MailTo = admin1 admin2 admin3 Range = yesterday Detail = Medium HostName = www.example.com Print = No Output = mail Format = html <end /etc/logwatch/conf/logwatch.conf> The same settings in Debian/Ubuntu servers send the reports in HTML format. In my search, I did not come across any solution for CentOS 6. Any ideas on how to get logwatch to generate HTML reports? Thanks for your help. -- Arun Khan

2 8

Re: [CentOS] group write permissions not being respected
by Gordon Messmer 31 Aug '16

31 Aug '16

On 08/30/2016 03:01 PM, Pat Haley wrote: > the owner of a directory can still write to that directory but any > other member of the associated group cannot, even though the directory > clearly has group write permissions set Use "getfacl" on both the client and server side to view the complete permission set. What do those look like?

1 0

NODEJS010-NPM is not getting installed due to dependency errors on Custom Centos ISO installation
by SUDHANSHU BHUTANI 31 Aug '16

31 Aug '16

Hi, I have built successfully all the dependent packages of nodejs010 and npm. I have used following command:- *rpmbuild --define 'scl nodejs010' --bb SPEC/name_of_spec.spec* Following is the list of RPMs cloned and built from GIT:- nodejs010-2.1-5.el7.centos.x86_64.rpm nodejs010-http-parser-2.0-6.20121128gitcd01361.el7.centos.x86_64.rpm nodejs010-http-parser-devel-2.0-6.20121128gitcd01361.el7.centos.x86_64.rpm nodejs010-libuv-0.10.30-1.el7.centos.x86_64.rpm nodejs010-libuv-devel-0.10.30-1.el7.centos.x86_64.rpm nodejs010-node-gyp-3.2.0-2.el7.centos.noarch.rpm nodejs010-nodejs-0.10.40-1.el7.centos.x86_64.rpm nodejs010-nodejs-abbrev-1.0.5-1.el7.centos.noarch.rpm nodejs010-nodejs-ansi-0.3.0-1.el7.centos.noarch.rpm nodejs010-nodejs-ansicolors-0.3.2-1.el7.centos.noarch.rpm nodejs010-nodejs-ansistyles-0.1.3-1.el7.centos.x86_64.rpm nodejs010-nodejs-archy-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.noarch.rpm nodejs010-nodejs-array-index-0.1.1-1.el7.centos.noarch.rpm nodejs010-nodejs-asap-1.0.0-4.el7.centos.noarch.rpm nodejs010-nodejs-async-some-1.0.2-2.el7.centos.noarch.rpm nodejs010-nodejs-balanced-match-0.2.1-2.el7.centos.noarch.rpm nodejs010-nodejs-bl-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-block-stream-0.0.7-2.el7.centos.noarch.rpm nodejs010-nodejs-brace-expansion-1.1.1-2.el7.centos.noarch.rpm nodejs010-nodejs-builtin-modules-1.1.0-1.el7.centos.noarch.rpm nodejs010-nodejs-builtins-1.0.2-2.el7.centos.noarch.rpm nodejs010-nodejs-caseless-0.11.0-1.el7.centos.noarch.rpm nodejs010-nodejs-char-spinner-1.0.1-2.el7.centos.noarch.rpm nodejs010-nodejs-chmodr-1.0.2-1.el7.centos.noarch.rpm nodejs010-nodejs-chownr-1.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-clone-0.2.0-3.el7.centos.noarch.rpm nodejs010-nodejs-cmd-shim-2.0.0-2.el7.centos.noarch.rpm nodejs010-nodejs-columnify-1.3.2-3.el7.centos.noarch.rpm nodejs010-nodejs-concat-map-0.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-concat-stream-1.4.4-5.el7.centos.noarch.rpm nodejs010-nodejs-config-chain-1.1.9-1.el7.centos.noarch.rpm nodejs010-nodejs-core-util-is-1.0.1-2.el7.centos.noarch.rpm nodejs010-nodejs-debug-2.2.0-2.el7.centos.noarch.rpm nodejs010-nodejs-debuglog-1.0.1-4.el7.centos.noarch.rpm nodejs010-nodejs-defaults-1.0.0-5.el7.centos.noarch.rpm nodejs010-nodejs-delegates-0.1.0-1.el7.centos.noarch.rpm nodejs010-nodejs-devel-0.10.40-1.el7.centos.x86_64.rpm nodejs010-nodejs-dezalgo-1.0.2-3.el7.centos.noarch.rpm nodejs010-nodejs-editor-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-forever-agent-0.5.0-2.el7.centos.noarch.rpm nodejs010-nodejs-fstream-1.0.3-2.el7.centos.noarch.rpm nodejs010-nodejs-fstream-ignore-1.0.2-1.el7.centos.noarch.rpm nodejs010-nodejs-fstream-npm-1.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-fs-vacuum-1.2.6-3.el7.centos.noarch.rpm nodejs010-nodejs-fs-write-stream-atomic-1.0.3-3.el7.centos.noarch.rpm nodejs010-nodejs-gauge-1.2.2-3.el7.centos.noarch.rpm nodejs010-nodejs-github-url-from-git-1.4.0-1.el7.centos.noarch.rpm nodejs010-nodejs-github-url-from-username-repo-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-glob-5.0.15-1.el7.centos.noarch.rpm nodejs010-nodejs-graceful-fs-4.1.2-3.el7.centos.noarch.rpm nodejs010-nodejs-has-unicode-2.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-hosted-git-info-2.1.4-3.el7.centos.noarch.rpm nodejs010-nodejs-inflight-1.0.4-2.el7.centos.noarch.rpm nodejs010-nodejs-inherits-2.0.0-13.el7.centos.noarch.rpm nodejs010-nodejs-ini-1.2.0-1.el7.centos.noarch.rpm nodejs010-nodejs-init-package-json-1.9.1-1.el7.centos.noarch.rpm nodejs010-nodejs-is-absolute-0.2.3-3.el7.centos.noarch.rpm nodejs010-nodejs-isarray-0.0.1-3.el7.centos.noarch.rpm nodejs010-nodejs-is-builtin-module-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-is-relative-0.2.1-2.el7.centos.noarch.rpm nodejs010-nodejs-is-unc-path-0.1.1-2.el7.centos.noarch.rpm nodejs010-nodejs-is-windows-0.1.0-3.el7.centos.noarch.rpm nodejs010-nodejs-jju-1.2.1-1.el7.centos.noarch.rpm nodejs010-nodejs-json-parse-helpfulerror-1.0.3-1.el7.centos.noarch.rpm nodejs010-nodejs-json-stringify-safe-5.0.0-2.el7.centos.noarch.rpm nodejs010-nodejs-lockfile-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-lodash._basetostring-3.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-lodash._createpadding-3.6.1-1.el7.centos.noarch.rpm nodejs010-nodejs-lodash.pad-3.1.1-1.el7.centos.noarch.rpm nodejs010-nodejs-lodash.padleft-3.1.1-1.el7.centos.noarch.rpm nodejs010-nodejs-lodash.padright-3.1.1-1.el7.centos.noarch.rpm nodejs010-nodejs-lodash.repeat-3.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-lru-cache-2.7.0-1.el7.centos.noarch.rpm nodejs010-nodejs-mime-db-1.15.0-3.el7.centos.noarch.rpm nodejs010-nodejs-mime-types-2.1.3-1.el7.centos.noarch.rpm nodejs010-nodejs-minimatch-3.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-minimist-0.0.8-1.el7.centos.noarch.rpm nodejs010-nodejs-mkdirp-0.5.0-1.el7.centos.noarch.rpm nodejs010-nodejs-ms-0.7.1-2.el7.centos.noarch.rpm nodejs010-nodejs-mute-stream-0.0.4-3.el7.centos.noarch.rpm nodejs010-nodejs-node-uuid-1.4.1-2.el7.centos.noarch.rpm nodejs010-nodejs-nopt-3.0.6-1.el7.centos.noarch.rpm nodejs010-nodejs-normalize-git-url-3.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-normalize-package-data-2.3.5-1.el7.centos.noarch.rpm nodejs010-nodejs-npm-cache-filename-1.0.2-1.el7.centos.noarch.rpm nodejs010-nodejs-npm-install-checks-1.0.6-1.el7.centos.noarch.rpm nodejs010-nodejs-npmlog-2.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-npm-package-arg-4.1.0-1.el7.centos.noarch.rpm nodejs010-nodejs-npm-registry-client-7.0.8-1.el7.centos.noarch.rpm nodejs010-nodejs-npm-user-validate-0.1.1-1.el7.centos.noarch.rpm nodejs010-nodejs-once-1.3.0-1.el7.centos.noarch.rpm nodejs010-nodejs-opener-1.4.1-1.el7.centos.noarch.rpm nodejs010-nodejs-osenv-0.1.3-1.el7.centos.noarch.rpm nodejs010-nodejs-os-homedir-1.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-os-tmpdir-1.0.1-3.el7.centos.noarch.rpm nodejs010-nodejs-path-array-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-path-is-absolute-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-path-is-inside-1.0.0-1.el7.centos.x86_64.rpm nodejs010-nodejs-process-nextick-args-1.0.2-1.el7.centos.noarch.rpm nodejs010-nodejs-promzard-0.2.0-7.el7.centos.noarch.rpm nodejs010-nodejs-proto-list-1.2.2-5.el7.centos.noarch.rpm nodejs010-nodejs-qs-0.6.5-5.el7.centos.noarch.rpm nodejs010-nodejs-read-1.0.5-1.el7.centos.noarch.rpm nodejs010-nodejs-readable-stream-2.0.2-3.el7.centos.noarch.rpm nodejs010-nodejs-readdir-scoped-modules-1.0.2-1.el7.centos.noarch.rpm nodejs010-nodejs-read-installed-4.0.3-1.el7.centos.noarch.rpm nodejs010-nodejs-read-package-json-2.0.2-1.el7.centos.noarch.rpm nodejs010-nodejs-realize-package-specifier-3.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-request-2.42.0-6.el7.centos.noarch.rpm nodejs010-nodejs-retry-0.6.0-6.el7.centos.noarch.rpm nodejs010-nodejs-rimraf-2.4.3-1.el7.centos.noarch.rpm nodejs010-nodejs-semver-5.0.3-1.el7.centos.noarch.rpm nodejs010-nodejs-sha-2.0.1-2.1.el7.centos.noarch.rpm nodejs010-nodejs-slide-1.1.6-1.el7.centos.noarch.rpm nodejs010-nodejs-sorted-object-1.0.0-3.el7.centos.noarch.rpm nodejs010-nodejs-spdx-correct-1.0.2-1.el7.centos.noarch.rpm nodejs010-nodejs-spdx-exceptions-1.0.4-1.el7.centos.noarch.rpm nodejs010-nodejs-spdx-expression-parse-1.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-spdx-license-ids-1.0.1-2.el7.centos.noarch.rpm nodejs010-nodejs-string_decoder-0.10.31-1.el7.centos.noarch.rpm nodejs010-nodejs-strip-ansi-0.2.0-1.el7.centos.noarch.rpm nodejs010-nodejs-tar-2.2.1-1.el7.centos.noarch.rpm nodejs010-nodejs-text-table-0.2.0-1.el7.centos.x86_64.rpm nodejs010-nodejs-tunnel-agent-0.3.0-2.el7.centos.noarch.rpm nodejs010-nodejs-uid-number-0.0.5-1.el7.centos.noarch.rpm nodejs010-nodejs-umask-1.1.0-4.el7.centos.noarch.rpm nodejs010-nodejs-unc-path-regex-0.1.1-2.el7.centos.noarch.rpm nodejs010-nodejs-util-deprecate-1.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-util-extend-1.0.1-4.el7.centos.noarch.rpm nodejs010-nodejs-validate-npm-package-license-3.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-validate-npm-package-name-2.2.2-3.el7.centos.noarch.rpm nodejs010-nodejs-wcwidth-1.0.0-4.el7.centos.noarch.rpm nodejs010-nodejs-which-1.2.0-1.el7.centos.noarch.rpm nodejs010-nodejs-wrappy-1.0.1-2.el7.centos.noarch.rpm nodejs010-nodejs-write-file-atomic-1.1.2-3.el7.centos.noarch.rpm nodejs010-npm-2.14.13-7.el7.centos.noarch.rpm nodejs010-runtime-2.1-5.el7.centos.x86_64.rpm nodejs010-scldevel-2.1-5.el7.centos.x86_64.rpm *However, when we copy these RPMS to our ISO, anaconda installer fails to install due to dependency errors:-* nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.noarch requires nodejs010-npm(readable-stream) < 2 nodejs010-nodejs-cmd-shim-2.0.0-2.el7.centos.noarch requires nodejs010-npm(graceful-fs) < 4 nodejs010-nodejs-columnify-1.3.2-3.el7.centos.noarch requires nodejs010-npm(strip-ansi) >= 2.0.0 nodejs010-nodejs-fstream-ignore-1.0.2-1.el7.centos.noarch requires nodejs010-npm(minimatch) < 3 nodejs010-nodejs-gauge-1.2.2-3.el7.centos.noarch requires nodejs010-npm(has-unicode) < 2 nodejs010-nodejs-init-package-json-1.9.1-1.el7.centos.noarch requires nodejs010-npm(promzard) >= 0.3.0 nodejs010-nodejs-npm-registry-client-7.0.8-1.el7.centos.noarch requires nodejs010-npm(concat-stream) >= 1.4.6 nodejs010-nodejs-npm-registry-client-7.0.8-1.el7.centos.noarch requires nodejs010-npm(request) >= 2.47.0 nodejs010-nodejs-npm-registry-client-7.0.8-1.el7.centos.noarch requires nodejs010-npm(retry) >= 0.8.0 nodejs010-nodejs-which-1.2.0-1.el7.centos.noarch requires nodejs010-npm(is-absolute) < 0.2 How is it possible, to get these errors, how come packages are not satisfying minimum dependency for working of NPM? If i do yumdownloader for all these above RPMs from repo: [centos-sclo-rh] : http://mirror.centos.org/centos/7/sclo/x86_64/rh/nodejs010/), then i get following RPMs without "centos" name:- nodejs010-2.1-5.el7.x86_64.rpm nodejs010-http-parser-2.0-6.20121128gitcd01361.el7.x86_64.rpm nodejs010-http-parser-devel-2.0-6.20121128gitcd01361.el7.x86_64.rpm nodejs010-libuv-0.10.30-1.el7.x86_64.rpm nodejs010-libuv-devel-0.10.30-1.el7.x86_64.rpm nodejs010-node-gyp-3.2.0-2.el7.noarch.rpm nodejs010-nodejs-0.10.40-1.el7.x86_64.rpm nodejs010-nodejs-abbrev-1.0.5-1.el7.noarch.rpm nodejs010-nodejs-ansi-0.3.0-2.el7.noarch.rpm nodejs010-nodejs-ansicolors-0.3.2-1.el7.noarch.rpm nodejs010-nodejs-ansistyles-0.1.3-1.el7.x86_64.rpm nodejs010-nodejs-archy-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.noarch.rpm nodejs010-nodejs-array-index-0.1.1-1.el7.noarch.rpm nodejs010-nodejs-asap-1.0.0-4.el7.noarch.rpm nodejs010-nodejs-async-some-1.0.2-2.el7.noarch.rpm nodejs010-nodejs-balanced-match-0.2.1-2.el7.noarch.rpm nodejs010-nodejs-bl-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-block-stream-0.0.7-2.el7.noarch.rpm nodejs010-nodejs-brace-expansion-1.1.1-2.el7.noarch.rpm nodejs010-nodejs-builtin-modules-1.1.0-1.el7.noarch.rpm nodejs010-nodejs-builtins-1.0.2-2.el7.noarch.rpm nodejs010-nodejs-caseless-0.11.0-1.el7.noarch.rpm nodejs010-nodejs-char-spinner-1.0.1-2.el7.noarch.rpm nodejs010-nodejs-chmodr-1.0.2-1.el7.noarch.rpm nodejs010-nodejs-chownr-1.0.1-1.el7.noarch.rpm nodejs010-nodejs-clone-0.2.0-3.el7.noarch.rpm nodejs010-nodejs-cmd-shim-2.0.0-2.el7.noarch.rpm nodejs010-nodejs-columnify-1.3.2-3.el7.noarch.rpm nodejs010-nodejs-concat-map-0.0.1-1.el7.noarch.rpm nodejs010-nodejs-concat-stream-1.4.4-5.el7.noarch.rpm nodejs010-nodejs-config-chain-1.1.9-1.el7.noarch.rpm nodejs010-nodejs-core-util-is-1.0.1-2.el7.noarch.rpm nodejs010-nodejs-debug-2.2.0-2.el7.noarch.rpm nodejs010-nodejs-debuglog-1.0.1-4.el7.noarch.rpm nodejs010-nodejs-defaults-1.0.0-5.el7.noarch.rpm nodejs010-nodejs-delegates-0.1.0-1.el7.noarch.rpm nodejs010-nodejs-devel-0.10.40-1.el7.x86_64.rpm nodejs010-nodejs-dezalgo-1.0.2-3.el7.noarch.rpm nodejs010-nodejs-editor-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-forever-agent-0.5.0-2.el7.noarch.rpm nodejs010-nodejs-fstream-1.0.3-2.el7.noarch.rpm nodejs010-nodejs-fstream-ignore-1.0.2-1.el7.noarch.rpm nodejs010-nodejs-fstream-npm-1.0.1-1.el7.noarch.rpm nodejs010-nodejs-fs-vacuum-1.2.6-3.el7.noarch.rpm nodejs010-nodejs-fs-write-stream-atomic-1.0.3-3.el7.noarch.rpm nodejs010-nodejs-gauge-1.2.2-3.el7.noarch.rpm nodejs010-nodejs-github-url-from-git-1.4.0-1.el7.noarch.rpm nodejs010-nodejs-github-url-from-username-repo-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-glob-5.0.15-1.el7.noarch.rpm nodejs010-nodejs-graceful-fs-4.1.2-3.el7.noarch.rpm nodejs010-nodejs-has-unicode-2.0.0-1.el7.noarch.rpm nodejs010-nodejs-hosted-git-info-2.1.4-3.el7.noarch.rpm nodejs010-nodejs-inflight-1.0.4-2.el7.noarch.rpm nodejs010-nodejs-inherits-2.0.0-13.el7.noarch.rpm nodejs010-nodejs-ini-1.2.0-1.el7.noarch.rpm nodejs010-nodejs-init-package-json-1.9.1-1.el7.noarch.rpm nodejs010-nodejs-is-absolute-0.2.3-3.el7.noarch.rpm nodejs010-nodejs-isarray-0.0.1-3.el7.noarch.rpm nodejs010-nodejs-is-builtin-module-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-is-relative-0.2.1-2.el7.noarch.rpm nodejs010-nodejs-is-unc-path-0.1.1-2.el7.noarch.rpm nodejs010-nodejs-is-windows-0.1.0-3.el7.noarch.rpm nodejs010-nodejs-jju-1.2.1-1.el7.noarch.rpm nodejs010-nodejs-json-parse-helpfulerror-1.0.3-1.el7.noarch.rpm nodejs010-nodejs-json-stringify-safe-5.0.0-2.el7.noarch.rpm nodejs010-nodejs-lockfile-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-lodash._basetostring-3.0.1-1.el7.noarch.rpm nodejs010-nodejs-lodash._createpadding-3.6.1-1.el7.noarch.rpm nodejs010-nodejs-lodash.pad-3.1.1-1.el7.noarch.rpm nodejs010-nodejs-lodash.padleft-3.1.1-1.el7.noarch.rpm nodejs010-nodejs-lodash.padright-3.1.1-1.el7.noarch.rpm nodejs010-nodejs-lodash.repeat-3.0.1-1.el7.noarch.rpm nodejs010-nodejs-lru-cache-2.7.0-1.el7.noarch.rpm nodejs010-nodejs-mime-db-1.15.0-3.el7.noarch.rpm nodejs010-nodejs-mime-types-2.1.3-1.el7.noarch.rpm nodejs010-nodejs-minimatch-3.0.0-1.el7.noarch.rpm nodejs010-nodejs-minimist-0.0.8-1.el7.noarch.rpm nodejs010-nodejs-mkdirp-0.5.0-1.el7.noarch.rpm nodejs010-nodejs-ms-0.7.1-2.el7.noarch.rpm nodejs010-nodejs-mute-stream-0.0.4-3.el7.noarch.rpm nodejs010-nodejs-node-uuid-1.4.1-2.el7.noarch.rpm nodejs010-nodejs-nopt-3.0.6-1.el7.noarch.rpm nodejs010-nodejs-normalize-git-url-3.0.1-1.el7.noarch.rpm nodejs010-nodejs-normalize-package-data-2.3.5-1.el7.noarch.rpm nodejs010-nodejs-npm-cache-filename-1.0.2-1.el7.noarch.rpm nodejs010-nodejs-npm-install-checks-1.0.6-1.el7.noarch.rpm nodejs010-nodejs-npmlog-2.0.0-1.el7.noarch.rpm nodejs010-nodejs-npm-package-arg-4.1.0-1.el7.noarch.rpm nodejs010-nodejs-npm-registry-client-7.0.8-1.el7.noarch.rpm nodejs010-nodejs-npm-user-validate-0.1.1-1.el7.noarch.rpm nodejs010-nodejs-once-1.3.0-1.el7.noarch.rpm nodejs010-nodejs-opener-1.4.1-1.el7.noarch.rpm nodejs010-nodejs-osenv-0.1.3-1.el7.noarch.rpm nodejs010-nodejs-os-homedir-1.0.1-1.el7.noarch.rpm nodejs010-nodejs-os-tmpdir-1.0.1-3.el7.noarch.rpm nodejs010-nodejs-path-array-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-path-is-absolute-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-path-is-inside-1.0.0-1.el7.x86_64.rpm nodejs010-nodejs-process-nextick-args-1.0.2-1.el7.noarch.rpm nodejs010-nodejs-promzard-0.2.0-7.el7.noarch.rpm nodejs010-nodejs-proto-list-1.2.2-5.el7.noarch.rpm nodejs010-nodejs-qs-1.2.2-1.el7.noarch.rpm nodejs010-nodejs-read-1.0.5-1.el7.noarch.rpm nodejs010-nodejs-readable-stream-2.0.2-3.el7.noarch.rpm nodejs010-nodejs-readdir-scoped-modules-1.0.2-1.el7.noarch.rpm nodejs010-nodejs-read-installed-4.0.3-1.el7.noarch.rpm nodejs010-nodejs-read-package-json-2.0.2-1.el7.noarch.rpm nodejs010-nodejs-realize-package-specifier-3.0.1-1.el7.noarch.rpm nodejs010-nodejs-request-2.42.0-6.el7.noarch.rpm nodejs010-nodejs-retry-0.6.0-6.el7.noarch.rpm nodejs010-nodejs-rimraf-2.4.3-1.el7.noarch.rpm nodejs010-nodejs-semver-5.0.3-1.el7.noarch.rpm nodejs010-nodejs-sha-2.0.1-2.1.el7.noarch.rpm nodejs010-nodejs-slide-1.1.6-1.el7.noarch.rpm nodejs010-nodejs-sorted-object-1.0.0-3.el7.noarch.rpm nodejs010-nodejs-spdx-correct-1.0.2-1.el7.noarch.rpm nodejs010-nodejs-spdx-exceptions-1.0.4-1.el7.noarch.rpm nodejs010-nodejs-spdx-expression-parse-1.0.1-1.el7.noarch.rpm nodejs010-nodejs-spdx-license-ids-1.0.1-2.el7.noarch.rpm nodejs010-nodejs-string_decoder-0.10.31-1.el7.noarch.rpm nodejs010-nodejs-strip-ansi-0.2.0-1.el7.noarch.rpm nodejs010-nodejs-tar-2.2.1-1.el7.noarch.rpm nodejs010-nodejs-text-table-0.2.0-1.el7.x86_64.rpm nodejs010-nodejs-tunnel-agent-0.3.0-2.el7.noarch.rpm nodejs010-nodejs-uid-number-0.0.5-1.el7.noarch.rpm nodejs010-nodejs-umask-1.1.0-4.el7.noarch.rpm nodejs010-nodejs-unc-path-regex-0.1.1-2.el7.noarch.rpm nodejs010-nodejs-util-deprecate-1.0.1-1.el7.noarch.rpm nodejs010-nodejs-util-extend-1.0.1-4.el7.noarch.rpm nodejs010-nodejs-validate-npm-package-license-3.0.1-1.el7.noarch.rpm nodejs010-nodejs-validate-npm-package-name-2.2.2-3.el7.noarch.rpm nodejs010-nodejs-wcwidth-1.0.0-4.el7.noarch.rpm nodejs010-nodejs-which-1.2.0-1.el7.noarch.rpm nodejs010-nodejs-wrappy-1.0.1-2.el7.noarch.rpm nodejs010-nodejs-write-file-atomic-1.1.2-3.el7.noarch.rpm nodejs010-npm-2.14.13-6.el7.noarch.rpm nodejs010-runtime-2.1-5.el7.x86_64.rpm *If i copy paste above RPMS to my custom ISO, then anaconda successfully installs these packages, without any errors* *What is there is these already built RPMs (taken from repo: [centos-sclo-rh] : http://mirror.centos.org/centos/7/sclo/x86_64/rh/nodejs010/) which is not there in my built RPMS?* Any pointers for this, as we feel, there is some inconsistency in the version available on git.centos.org/git/rpms/<name_of_pkg>.git ? Regards Sudhanshu Bhutani

2 1

None
by None 30 Aug '16

30 Aug '16

by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u7UM1iPO028599 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <centos(a)centos.org>; Tue, 30 Aug 2016 18:01:45 -0400 To: centos(a)centos.org From: Pat Haley <phaley(a)mit.edu> Message-ID: <d059a28c-b866-5056-dda6-29e3077ca907(a)mit.edu> Date: Tue, 30 Aug 2016 18:01:44 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrPIsWRmVeSWpSXmKPExsUixG6nouvFdCzc4PUCIYtlZxYwOzB6rGyb zBzAGMVlk5Kak1mWWqRvl8CV0bNoOlPBCc6KTQ9PsDcwTmfvYuTkkBAwkXjZsomti5GLQ0ig jUni8MVtUM5JRokZM6ZAOQeZJKY/2c8I0iIiICrRs/gVG4jNJqAgse7WGbBRwkCjmldeZAKx eQWsJL43bQezWQRUJeZOaGcGsUUFIiRurfrICFEjKHFy5hMWEJtZwExi3uaHzBC2vMT2t3OY JzDyzkJSNgtJ2SwkZQsYmVcxyqbkVunmJmbmFKcm6xYnJ+blpRbpGurlZpbopaaUbmIEhROn JM8OxjNvvA4xCnAwKvHwZsw4Gi7EmlhWXJl7iFGSg0lJlDf8L1CILyk/pTIjsTgjvqg0J7X4 EKMEB7OSCO91xmPhQrwpiZVVqUX5MClpDhYlcd6uGQfChQTSE0tSs1NTC1KLYLIyHBxKErw7 QBoFi1LTUyvSMnNKENJMHJwgw3mAhnuDDS8uSMwtzkyHyJ9iVJQS5xUFSQiAJDJK8+B6wfGu xn7oFaM40CvCvJcYgKp4gKkCrvsV0GAmoMEFdw6DDC5JREhJNTDOn+LY8sOJSVhFfnV4VzaH T8iDcx+0dvn36Fluta5/vWa3rODTN3LmNl7/W21uh59fwpKvfHjqMtdZ9z/tc/MKZN9/zYhn ocKdJ3P7bu9nyWx6U+Q44dhR8+nzNdf0b5hqFX9bxvtEguS/b/MebPXkTHr/ZmV4+PPttabT hGf57usu5fV/dH+mEktxRqKhFnNRcSIAKBIMXtICAAA= Subject: [CentOS] group write permissions not being respected X-BeenThere: centos(a)centos.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe: <https://lists.centos.org/mailman/options/centos>, <mailto:centos-request@centos.org?subject=unsubscribe> List-Archive: <http://lists.centos.org/pipermail/centos/> List-Post: <mailto:centos@centos.org> List-Help: <mailto:centos-request@centos.org?subject=help> List-Subscribe: <https://lists.centos.org/mailman/listinfo/centos>, <mailto:centos-request@centos.org?subject=subscribe> X-List-Received-Date: Tue, 30 Aug 2016 22:01:46 -0000 Hi We have just migrated our data to a new file server (more space, old server was showing its age). We have a volume for collaborative use, based on group membership. In our new server, the group write permissions are not being respected (e.g. the owner of a directory can still write to that directory but any other member of the associated group cannot, even though the directory clearly has group write permissions set). This is occurring regardless of how many groups the user is a member of (i.e. users that are members of fewer then 16 groups are still affected). the relevant fstab line from the server looks like localhost:/data-volume /gdata glusterfs defaults 0 0 and for a client: mseas-data2:/gdata /gdata nfs defaults 0 0 Any help would be greatly appreciated. Thanks -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley(a)mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301

1 0

None
by None 30 Aug '16

30 Aug '16

by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u7ULNSNq006624 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <centos(a)centos.org>; Tue, 30 Aug 2016 17:23:29 -0400 To: centos(a)centos.org References: <d80864bd-9497-86be-d8db-cdf3c0378d7c(a)mit.edu> <20160829172355.849cf429eb17bf94dd738fa0(a)melvilletheatre.com> From: Pat Haley <phaley(a)mit.edu> Message-ID: <2e155be1-9265-a189-724b-3ab2659d38dc(a)mit.edu> Date: Tue, 30 Aug 2016 17:23:27 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160829172355.849cf429eb17bf94dd738fa0(a)melvilletheatre.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrKIsWRmVeSWpSXmKPExsUixCmqrRv082i4wc2bKhbLzixgdmD0WNk2 mTmAMYrLJiU1J7MstUjfLoErY8oKr4I7QhWPvy9mbmC8xdfFyMkhIWAiMeHnW7YuRi4OIYE2 Jonvr+8xQTgnGSWeblnADuEcZJI4+7aHGaRFWMBB4s/PdjYQW0RAVKJn8SswW0igSuL9pIus IDabgILEultngJo5OHgFrCTurdECCbMIqErs7pjBAmKLCkRI3Fr1kRHE5hUQlDg58wlYnFPA S2LpSpBWTg5mAVuJO3N3M0PY8hLb385hnsDIPwtJyywkZbOQlC1gZF7FKJuSW6Wbm5iZU5ya rFucnJiXl1qka6aXm1mil5pSuokRFHrsLso7GF/2eR9iFOBgVOLhzZhxNFyINbGsuDL3EKMk B5OSKO+eDqAQX1J+SmVGYnFGfFFpTmrxIUYJDmYlEd7P34ByvCmJlVWpRfkwKWkOFiVx3q4Z B8KFBNITS1KzU1MLUotgsjIcHEoSvJe/AzUKFqWmp1akZeaUIKSZODhBhvMADZf8ATK8uCAx tzgzHSJ/ilFRSpz3JchWAZBERmkeXC84NaixH3rFKA70ijDvBJB2HmBaget+BTSYCWhwwZ3D IINLEhFSUg2MXoXXLeI4mYVE/+/6wH6wcoE9U0T+PJM1BlkHD9Wf0vBY8KxlmrXtvGccL6Sj 7i79srzxJr9ZlPiykLwtlgyeWz8o+dev1xDPb1llFMNy/n4Bx6+UoNfBix8Hq6552ppktzJu y4MgFr6g7y9qb/DKnzLobU95usB1rsxeP72OdVU5x4UWtz9SYinOSDTUYi4qTgQA4LNe++gC AAA= Subject: Re: [CentOS] CentOS 6: files now owned by nobody:nobody X-BeenThere: centos(a)centos.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe: <https://lists.centos.org/mailman/options/centos>, <mailto:centos-request@centos.org?subject=unsubscribe> List-Archive: <http://lists.centos.org/pipermail/centos/> List-Post: <mailto:centos@centos.org> List-Help: <mailto:centos-request@centos.org?subject=help> List-Subscribe: <https://lists.centos.org/mailman/listinfo/centos>, <mailto:centos-request@centos.org?subject=subscribe> X-List-Received-Date: Tue, 30 Aug 2016 21:23:31 -0000 The setting the Domain = line in /etc/idmapd.conf option solved our problem Thanks On 08/29/2016 07:23 PM, Frank Cox wrote: > On Mon, 29 Aug 2016 18:59:31 -0400 > Pat Haley wrote: > >> We noticed that all the files were owned by nobody > Here are my notes for dealing with this issue: > > If all users come up as nobody on a nfs mount: > > Add nfs server name to the Domain = line in /etc/idmapd.conf on both the server and the clients, i.e. Domain = nameof.server > > /sbin/service rpcidmapd restart > /sbin/service nfslock restart > /sbin/service nfs restart > > Also, the complete hostname as specified (nameof.server) must be in /etc/hosts on the nfs clients as well as the server > > --------------- > try > /usr/sbin/nfsidmap -c > on the client. > Since I put this into my /etc/rc.local , I don't have the problem any > longer. > --------------- > 1) /etc/idmapd.conf > # Set domain to the domain name shared by your NFS servers. > Domain: mycompany.com > Set local-realms to the name of the nfs servers you'll be using. THIS > WASN'T MENTIONED ELSEWHERE. > Local-Realms: nfs1.mycompany.com,nfs2.mycompany.com > # make the above changes on all the servers in question. > > 2) /etc/hosts: list with all the NFS servers you specified in local-realms above. This way DNS errors don't make your servers get hung > 1.2.3.4 nfs1.mycompany.com > 1.2.3.5 nfs2.mycompany.com > > 3) Make sure you synchronize your /etc/passwd files so that the account > IDs match up or you'll get very strange results. > > 4) Reboot EVERYTHING. Restarting services was not enough. > For documentation's sake, I restarted rpcidmapd, nfslock, and nfs, but didn't get the correct permissions until reboot. It doesn't seem important to run the nfs service on the > clients. > > 5) Client mount: > # CLI > /bin/mount -t nfs servername:/path/to/share /local/mount/point > > # /etc/fstab > servername.com:/path/to/share /local/mount/mount nfs ro,nolock 0 0 > > # mount -a > > -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley(a)mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301

1 0

Re: [CentOS] CentOS 6: files now owned by nobody:nobody
by Jonathan Billings 30 Aug '16

30 Aug '16

On Mon, Aug 29, 2016 at 06:59:31PM -0400, Pat Haley wrote: > ... We > noticed that all the files were owned by nobody (with nobody as the group). If its NFSv4, then its most likely a problem with your idmapper. Make sure that the rpc.idmapd is running on your client, and that your server has appropriate ID mapping enabled. If its NFSv4, are you using sec=krb5*? -- Jonathan Billings <billings(a)negate.org>

2 1

.htaccess file
by TE Dukes 30 Aug '16

30 Aug '16

Hello, My home system on a DSL line is getting worn out by bad behavior robots. Awhile back, I created a .htaccess file that block countries by IP blocks. Its 2MB in size. I have been running Linux since Slackware 1.0 and moved to Redhat around 2.0. I started after running a BBS using a doorway for newsgroups. Been hooked ever since. So, today, I tried following the directions for apache.org website, https://httpd.apache.org/docs/current/howto/htaccess.html to move the .htaccess <https://httpd.apache.org/docs/current/howto/htaccess.html%20to%20move%20the %20.htaccess> file to a file located in a directory /var/www/htdocs. I'm just not following or understanding. The .htaccess file works but on a slow DSL, I don't want the hits. I added the following to my httpd.conf: <Directory "/var/www/htdocs"> AddType text/htdocs ".txt" </Directory> And copied my .htaccess to /var/www/htdocs as htaccess.txt In the example from the apache website, I don't get the: AddType text/example ".exm" Where did they come up .exm? TIA

6 16

None
by None 29 Aug '16

29 Aug '16

by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u7TNPWl1024422 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <centos(a)centos.org>; Mon, 29 Aug 2016 19:25:33 -0400 To: centos(a)centos.org References: <d80864bd-9497-86be-d8db-cdf3c0378d7c(a)mit.edu> <73650851-909c-c43a-a926-53cbdf14af6f(a)hogranch.com> From: Pat Haley <phaley(a)mit.edu> Message-ID: <7fe0f111-e54b-6f26-d816-a82851ddd0bd(a)mit.edu> Date: Mon, 29 Aug 2016 19:25:28 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <73650851-909c-c43a-a926-53cbdf14af6f(a)hogranch.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOIsWRmVeSWpSXmKPExsUixG6nrpt35Ei4wYsubotlZxYwOzB6rGyb zBzAGMVlk5Kak1mWWqRvl8CVcfjCYsaCi3wVl2beZGlgbObuYuTkkBAwkXi19idjFyMXh5BA G5PEgemTmSCck4wS7X9vsEM4B5kk7jx+wwzSIizgIPHnZzsbiC0iICrRs/gVmC0kUCBxcdVH JhCbTUBBYt2tM+wgNq+AlcSdttNgNSwCqhIbzy1hBLFFBSIkbq36yAhRIyhxcuYTFhCbE2j+ snOLwOYwC9hK3Jm7mxnClpfY/nYO8wRG/llIWmYhKZuFpGwBI/MqRtmU3Crd3MTMnOLUZN3i 5MS8vNQiXSO93MwSvdSU0k2MoPDjlOTdwfjvrtchRgEORiUeXgunI+FCrIllxZW5hxglOZiU RHmnxgOF+JLyUyozEosz4otKc1KLDzFKcDArifBmHgDK8aYkVlalFuXDpKQ5WJTEebtmHAgX EkhPLEnNTk0tSC2CycpwcChJ8EocBmoULEpNT61Iy8wpQUgzcXCCDOcBGv7zEMjw4oLE3OLM dIj8KUZFKXFeR5CEAEgiozQPrhecHtTYD71iFAd6RZj3EMgKHmBqget+BTSYCWhwwZ3DIINL EhFSUg2MtRuzrx96Znrb3Jt1f0vz9MNWL/5JBMb1/RXy/fB5Q+S907I8qTN2M14+rpuzfO68 mWuTyy+/PL6g0WS56+LWBIuKnRatOnlWseeTJ3M5RHeeDpqVttdg0RyGQBflxju85xlOVFzd 5/+Oy7lEeWp0Q1zWW7mp4m+9HzTMurBGZKFZZIeT2P1QJZbijERDLeai4kQAP19NXOoCAAA= Subject: Re: [CentOS] CentOS 6: files now owned by nobody:nobody X-BeenThere: centos(a)centos.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe: <https://lists.centos.org/mailman/options/centos>, <mailto:centos-request@centos.org?subject=unsubscribe> List-Archive: <http://lists.centos.org/pipermail/centos/> List-Post: <mailto:centos@centos.org> List-Help: <mailto:centos-request@centos.org?subject=help> List-Subscribe: <https://lists.centos.org/mailman/listinfo/centos>, <mailto:centos-request@centos.org?subject=subscribe> X-List-Received-Date: Mon, 29 Aug 2016 23:25:35 -0000 I believe NFSv4. On the machine that contains the physical disks (is that the "server" or the "NSF mount"?) the relevant line from /etc/fstab seems to be UUID=bde58f42-4ac4-4763-b0a8-f83723f0e2a0 /home ext4 defaults 1 2 while on my front-end machine its mseas-data2:/home /home nfs defaults 0 0 where mseas-data2 is the name of the machine that contains the physical disks. Note that it isn't just root that's becoming "nobody" but all the users Thanks On 08/29/2016 07:14 PM, John R Pierce wrote: > On 8/29/2016 3:59 PM, Pat Haley wrote: >> We are running a cluster under CentOS 6.6. We recently attached a >> new NAS device, running CentOS 6.8 and rsync'd our user file system >> to it. We noticed that all the files were owned by nobody (with >> nobody as the group). We copied over the /etc/passwd and /etc/group >> files from our front-end server to our NAS server. If we log in to >> the NAS server we see the files owned by their correct owners. >> However, doing an ls from the front-end server or any of the compute >> nodes still shows the files owned by "nobody". We rebooted one of >> the compute nodes but it still sees the files owned by nobody. > > a CentOS server isn't really a 'NAS device', as NAS implies an > appliance storage device. > > this is NFS? NFSv3, or NFSv4? what NFS options are on the server > and on the NFS mount? quite often NFS servers force root to nobody. > > -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley(a)mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301

1 0

Re: [CentOS] CentOS 6: files now owned by nobody:nobody
by Frank Cox 29 Aug '16

29 Aug '16

On Mon, 29 Aug 2016 18:59:31 -0400 Pat Haley wrote: > We noticed that all the files were owned by nobody Here are my notes for dealing with this issue: If all users come up as nobody on a nfs mount: Add nfs server name to the Domain = line in /etc/idmapd.conf on both the server and the clients, i.e. Domain = nameof.server /sbin/service rpcidmapd restart /sbin/service nfslock restart /sbin/service nfs restart Also, the complete hostname as specified (nameof.server) must be in /etc/hosts on the nfs clients as well as the server --------------- try /usr/sbin/nfsidmap -c on the client. Since I put this into my /etc/rc.local , I don't have the problem any longer. --------------- 1) /etc/idmapd.conf # Set domain to the domain name shared by your NFS servers. Domain: mycompany.com Set local-realms to the name of the nfs servers you'll be using. THIS WASN'T MENTIONED ELSEWHERE. Local-Realms: nfs1.mycompany.com,nfs2.mycompany.com # make the above changes on all the servers in question. 2) /etc/hosts: list with all the NFS servers you specified in local-realms above. This way DNS errors don't make your servers get hung 1.2.3.4 nfs1.mycompany.com 1.2.3.5 nfs2.mycompany.com 3) Make sure you synchronize your /etc/passwd files so that the account IDs match up or you'll get very strange results. 4) Reboot EVERYTHING. Restarting services was not enough. For documentation's sake, I restarted rpcidmapd, nfslock, and nfs, but didn't get the correct permissions until reboot. It doesn't seem important to run the nfs service on the clients. 5) Client mount: # CLI /bin/mount -t nfs servername:/path/to/share /local/mount/point # /etc/fstab servername.com:/path/to/share /local/mount/mount nfs ro,nolock 0 0 # mount -a -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss August 2016