search for: user_x

Displaying 4 results from an estimated 4 matches for "user_x".

Did you mean: user_u
2007 Dec 10
1
Different results depending on the user launching rsync
Hi Exactly the same command shows different rsync results depending on the user executing the rsync. If I execute rsync as root I get a proper result but if I execute as user_x there seems to be many files that require updating. Here is the command I execute /opt/local/bin/rsync -avuzhn --relative -e ssh --exclude-from=/TT_TCM/SEA/scripts/LMI/backup_exclude_files_norelative.t xt --rsync-path=/opt/local/bin/rsync /sea_bete_disk/LMI_IRELAND/ seaserv1lmi: I'm using r...
2006 Jul 28
1
nautilus pegging the cpu
I have a user that is running centos on many machines. At each machine, the users is logged into a common account that is located elsewhere on the network. Meaning that everyone is logged on as user_x and accessing the home directory via NFS. All users are running gnome. On some of the machines, the nautilus process is pegging the cpu. At this time, I have no strace or other info to indicate what nautilus is doing. Any ideas? -mark -- Mark Belanger LTX Corporation
2014 Feb 12
1
Where do I get detailed information about oplock-types and possible errors?
...e of our AD-users is having severe problems with frequent disconnections from the AD-Domain. I've noticed that the user has quite a lot error messages, that look like this: [2013/10/21 08:53:15.854203, 0] ../source3/smbd/oplock.c:333(oplock_timeout_handler) Oplock break failed for file user_x/Anwendungsdaten/Thunderbird/Profiles/pfo6pijp.default/panacea.dat -- replying anyway There's also something strage about the users locked files in smbstatus output: when any other user would use the oplock 'BATCH', the user with the problems always uses 'EXCLUSIVE+BATCH' 15...
2003 Nov 19
1
ssh tunnel exits unexptected
Hi, I have setup a tunnel from server A to server B across WAN by running "ssh -l user_X -L port_A:server_B:port_B server_C -N". Server B is in a private network, so I have to establish the tunnel via server C, which is in the same LAN with B but has a public IP. The problem is, every time I start the tunnel on server B, the tunnel process will die nearly two hours later. And i...