Assuming I have my license server installed here: /opt/jetbrains-license-server, how do I configure it to start automatically?
Chris Betti's questions
Using nfsstat -c
, I'm seeing a high "authrefrsh" (known as "newcred" on some systems) count on my NFS client pc for operations like ls
and find
on directories containing ~1000 files. This correlates with very poor performance (20+ minute directory listings). Cached NFS operations do not exhibit this behavior (the authrefrsh or the slowdown).
authrefrsh = calls every time I check nfsstat:
$ nfsstat -c
Client rpc stats:
calls retrans authrefrsh
280462 0 280462
Client nfs v3:
null getattr setattr lookup access readlink
0 0% 126990 45% 0 0% 10062 3% 58592 20% 0 0%
read write create mkdir symlink mknod
25030 8% 0 0% 65 0% 0 0% 2 0% 0 0%
remove rmdir rename link readdir readdirplus
0 0% 0 0% 0 0% 0 0% 0 0% 59654 21%
fsstat fsinfo pathconf commit
0 0% 20 0% 10 0% 0 0%
Connection details:
$ mount.nfs -v nfshost:/share/dir /somedir
mount.nfs: timeout set for Tue Feb 21 18:12:18 2012
mount.nfs: trying text-based options 'vers=4,addr=192.168.xx.xx,clientaddr=192.168.xx.xx'
mount.nfs: mount(2): Operation not permitted
mount.nfs: trying text-based options 'addr=192.168.xx.xx'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.xx.xx prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.xx.xx prog 100005 vers 3 prot UDP port 1011
nfshost:/share/dir on /somedir type nfs
nfshost RPC environment:
$ rpcinfo -T udp nfshost nfs
program 100003 version 2 ready and waiting
program 100003 version 3 ready and waiting
program 100003 version 4 ready and waiting
$ rpcinfo -T udp nfshost mountd
program 100005 version 1 ready and waiting
program 100005 version 2 ready and waiting
program 100005 version 3 ready and waiting
$ rpcinfo -T udp nfshost nlockmgr
program 100021 version 1 ready and waiting
rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 4
program 100021 version 2 is not available
program 100021 version 3 ready and waiting
program 100021 version 4 ready and waiting
$ rpcinfo -T udp nfshost llockmgr
rpcinfo: RPC: Program not registered
$ rpcinfo nfshost
program version netid address service owner
100000 2 tcp 0.0.0.0.0.111 portmapper unknown
100000 2 udp 0.0.0.0.0.111 portmapper unknown
100024 1 udp 0.0.0.0.2.212 status unknown
100024 1 tcp 0.0.0.0.2.215 status unknown
100021 1 udp 0.0.0.0.226.67 nlockmgr unknown
100021 3 udp 0.0.0.0.226.67 nlockmgr unknown
100021 4 udp 0.0.0.0.226.67 nlockmgr unknown
100021 1 tcp 0.0.0.0.134.55 nlockmgr unknown
100021 3 tcp 0.0.0.0.134.55 nlockmgr unknown
100021 4 tcp 0.0.0.0.134.55 nlockmgr unknown
100011 1 udp 0.0.0.0.3.230 rquotad unknown
100011 2 udp 0.0.0.0.3.230 rquotad unknown
100011 1 tcp 0.0.0.0.3.233 rquotad unknown
100011 2 tcp 0.0.0.0.3.233 rquotad unknown
100003 2 udp 0.0.0.0.8.1 nfs unknown
100003 3 udp 0.0.0.0.8.1 nfs unknown
100003 4 udp 0.0.0.0.8.1 nfs unknown
100003 2 tcp 0.0.0.0.8.1 nfs unknown
100003 3 tcp 0.0.0.0.8.1 nfs unknown
100003 4 tcp 0.0.0.0.8.1 nfs unknown
100005 1 udp 0.0.0.0.3.243 mountd unknown
100005 1 tcp 0.0.0.0.3.246 mountd unknown
100005 2 udp 0.0.0.0.3.243 mountd unknown
100005 2 tcp 0.0.0.0.3.246 mountd unknown
100005 3 udp 0.0.0.0.3.243 mountd unknown
100005 3 tcp 0.0.0.0.3.246 mountd unknown
Environment:
$ uname -a
Linux whiteheat 3.0.0-15-generic #26-Ubuntu SMP Fri Jan 20 17:23:00 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
$ mount.nfs a b -V
mount.nfs: (linux nfs-utils 1.2.4)
My hosting provider set up an Ubuntu-based virtual private server for me with three public IPs. I want to assign hostnames to those IPs as follows (I'm be using Dyn as my DNS):
- example.com -> IP_1
- www.example.com -> IP_1
- test.example.com -> IP_2
- admin.example.com -> IP_3
www.example.com will be the production site. test.example.com will be the bleeding edge version of the site, used for testing, and admin.example.com will expose a number of site administration services (e.g. SSH, rsyncd). Both www and test will be locked down to port 80. Both test and admin will only accept traffic from certain IPs.
I'm a little confused about the difference between the hostnames DNS deals with, and the server's hostname (as seen when running `hostname' on the server's command line). Where does the server's hostname come into play?
My guess is that Apache 2 doesn't care what the hostname
utility returns, because I can specify listening IP:PORT per VirtualHost. But, are they other services (or limitations) I should be aware of when connecting to my server via "foo.mydomain.com" if the machine's hostname is "randomname"?
I've got an ext3 filesystem sitting in a file, and I'd like to mount it to a local directory without sudo or any elevated permissions. Why? I'm creating a small filesystem for automated testing purposes. The automated tests run on machines I do not control, so there are some barriers to adding mount to sudoers.
Here's how I created the filesystem:
$ dd if=/dev/zero of=./50MB_partition count=102400
$ mkfs.ext3 -F 50MB_partition
Had I had permission, I could now mount it like so:
$ mkdir small_partition
$ sudo mount 50MB_partition ./small_partition
It seems that, because I own the filesystem and the mount point, there is no security risk associated with allowing me to mount this. I understand what is limiting me from calling mount without sudo; no explanation needed there. What I want to know is, is there a workaround that allows me to use my filesystem for testing purposes?