similar to: nfslock

Hello, booting starts /etc/init.d/nfslock. today, rpc.statd used port 873. later starting xinetd finds port used and disabled rsync daemon. So its more or less a lucky break, to boot CentOS and have rsync running? In /etc/rc3.d is S14nfslock S56xinetd so by design xinetd starts always after nfslock!!!! Best regards -- Viele Gr??e i.V. Helmut Drodofsky ________________________________

Hello, I am attempting to reload both nfs and nfslock when changing my exports configuration file. Unfortunately, I am unable to discern the correct syntax for making a single object subscribe to multiple objects. I have tried: => [nfs nfslock] => [nfs, nfslock] => [[nfs],[nfslock]] => [[nfs] [nfslock]] and none of them seem to work. Any assistance would be appreciated. Thank

I have two RHEL4 email servers running postfix/MailScanner which use dovecot. They work great. But during bootup the nfslock script in my init.d loads rpc.statd and calls portmap to get a port number. Portmap keeps giving rpc.statd the imaps port number (993). I then have to stop my mail server services, manually start dovecot, then restart the mail server services and everything goes merrily on

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, after upgrading to samba 3.0.8 (debian/unstable, i386) i too encounter similar problems as reported here: http://lists.samba.org/archive/samba/2004-November/095567.html upon logoff from a win2k(sp4) client, the profile cannot be saved and the samba logfile from the client (prinz) gives: [2004/11/26 17:57:06, 2]

This removes the appliance configuration bits from the installer and associated files since it has been deprecated --- installer/modules/ovirt/files/cobbler-import | 6 - .../modules/ovirt/files/ovirt-appliance-setup | 4 - installer/modules/ovirt/files/ovirt-storage | 73 ---------- installer/modules/ovirt/manifests/appliance.pp | 152 -------------------- 4 files

I've had the chance to use a testsystem here and couldn't resist running a few benchmark programs on them: bonnie++, tiobench, dbench and a few generic ones (cp/rm/tar/etc...) on ext{234}, btrfs, jfs, ufs, xfs, zfs. All with standard mkfs/mount options and +noatime for all of them. Here are the results, no graphs - sorry: http://nerdbynature.de/benchmarks/v40z/2009-12-22/ Reiserfs

I've had the chance to use a testsystem here and couldn't resist running a few benchmark programs on them: bonnie++, tiobench, dbench and a few generic ones (cp/rm/tar/etc...) on ext{234}, btrfs, jfs, ufs, xfs, zfs. All with standard mkfs/mount options and +noatime for all of them. Here are the results, no graphs - sorry: http://nerdbynature.de/benchmarks/v40z/2009-12-22/ Reiserfs

Hello, First and foremost, thanks *very* much for ctdb. It's a joy to use after banging around with other HA solutions. We're planning to use it to export Samba and NFS shares throughout campus. I'm having one problem with the NFS part though. When ctdbd first starts statd (we're using CTDB_MANAGES_NFS=yes), it does so without appending the stuff in the STATD_HOSTNAME variable

After getting a reasonably configured NFS4 setup working on my Scientific Linux server, I spent a majority of my evening trying to do the same with my Centos 5 box, with fruitless results. Most attempts to mount that server returns the following message: [root at sl01 log]# mount -t nfs4 192.168.15.200:/opt/company_data /mnt mount.nfs4: Operation not permitted As nearest as I can tell, I was

When writing to a newly created btrfs (vanilla 2.6.33-rc6, sparc64) the following messages are printed: [28617.650231] Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 [btrfs] [28617.745783] Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 [btrfs] [28654.589492] Kernel unaligned access at TPC[10101f18] btrfs_csum_final+0x38/0x60 [btrfs] [28654.685036] Kernel

Hi, all: Are there any blog tools which can use the openldap to authenticate the account or password? Could someone give some suggestions for it ? Thanks in advance... -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20100621/ad6bde73/attachment-0001.html>

Greetings, I have problem using Dom0 as NFS(v4)-server and DomU as client. When ever the client actually tries to copy data to nfs-server the virtual network (bridge) between the two hosts completely freezes and stops working. After this of course the client hangs waiting nfs-server to answer and server continues to try to contact nfslock daemon on the client. Dom0 is still accessible from

Hello all, I have been doing some searching for information about disabling services within a CentOS 5.5 install. I have found a few different opinions, and wanted to ask for some feedback. First off, the system is running a LAMP stack to serve a web application. It will only be doing email to send occasional messages out (sent via the application only). It will not be receiving email for any

https://bugzilla.mindrot.org/show_bug.cgi?id=1585 --- Comment #8 from mindrot at nerdbynature.de --- Created attachment 2274 --> https://bugzilla.mindrot.org/attachment.cgi?id=2274&action=edit Include option patch for OpenSSH 6.2 This is really just a modified version of Gavin Beatty's patch, slightly altered so it'll apply cleanly to OpenSSH 6.2 (i.e. yesterdays CVS checkout).

Hi, I am configuring firewall for NFS. I see that statd and mountd start at random port. Is there any way to force it to start at specific port each time. The '-p ' option would work, but how do I configure it to start at specific port number each time. I mean where do statd and mountd look for default configuration options? Any clues? - CS.

*sigh* The answer is that the large exported filesystem is a very large XFS... and at least through CentOS 6, upstream has *never* fixed an NFS bug that I find, googling, being complained about in '09: it gags on inodes > 32bit (not sure if that's signed, or unsigned, but....). The answer was to either create, or find an unneeded directory with a < 32bit inode, rename the

For some time now I have been puzzled as to why certain portions of my system boot were quite slow -- but only after journal recoveries. I was fearing that there was some ugly interaction between the recovery and the use of the journal shortly afterward but alas that is not the case. So just in case anybody else is seeing this problem and decides to try to hunt it down, let me save you some

--------------------------------------------------------------------- Red Hat, Inc. Security Advisory Synopsis: Revised advisory: Updated package for nfs-utils available Advisory ID: RHSA-2000:043-03 Issue date: 2000-07-17 Updated on: 2000-07-21 Product: Red Hat Linux Keywords: rpc.statd root compromise Cross references: N/A

Ralf Hildebrandt reported[0] the following messages on ext3-users: name_count maxed, losing inode data: dev=00:05, inode=5221 because the filesystem in question is indeed ext3. However, this warning is not generated by ext3 code but by the audit framework. While the origins of these messages are discussed elsewhere[1] the following patch modifies the printks in question so that users know

Hi all, I'm trying to setup this scenario on NFS and autofs on Centos 4.3: - useradd nfstest on an NFS server (192.168.1.247) - Setting up this NFS server /etc/exports: /home/nfstest 192.168.1.252/255.255.255.0(rw,sync,no_root_squash) - useradd nfstest on a client machine (192.168.1.252) - make sure that the uid and gid are the same on the server and the client - setting up