Re: [CentOS] Is Gnome in CentOS 5 ready for nfsv4?
Olaf Mueller wrote: > all my data are hosted by a server and exported with nfsv4. For > example if a user logs in on a client, /home and /data are exported > with nfsv4 and autofs. Now if the user delete some files, the > trashcan under gnome doesn't change its status nor doesn't show the > deleted files if opening the trashcan window. > Also the user isn't able to copy or move files between the exported > directories with nautilus, the error message is talking > about "different file systems". > > Is this a gnome-vfs2 bug in gnome-2.16? Really nobody here is using CentOS 5 as a gnome desktop with nfsv4 exported /home? thanks Olaf ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Samba problem after Up2date
ok... finally I get to solve my problem. I just have to start from the begining modifying the defaoult smb.conf file and then readd every samba user by "smbpasswd -a " command. This is my smb.conf: #smb.conf/ #=== Global Settings = [global] # --- Netwrok Related Options - # # workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH # # server string is the equivalent of the NT Description field # # netbios name can be used to specify a server name not tied to the hostname # # Interfaces lets you configure Samba to use multiple interfaces # If you have multiple network interfaces then you can list the ones # you want to listen on (never omit localhost) # # Hosts Allow/Hosts Deny lets you restrict who can connect, and you can # specifiy it as a per share option as well # workgroup = MAKIMET server string = Servidor Makimet netbios name = Servidor interfaces = lo eth0 192.168.0.10/24 hosts allow = 127.0.0 192.168.0. # --- Logging Options - # # Log File let you specify where to put logs and how to split them up. # # Max Log Size let you specify the max size log files should reach # logs split per machine log file = /var/log/samba/%m.log # max 100KB per log file, then rotate max log size = 100 # --- Standalone Server Options # # Scurity can be set to user, share(deprecated) or server(deprecated) # # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. security = user passdb backend = tdbsam # --- Domain Members Options # # Security must be set to domain or ads # # Use the realm option only with security = ads # Specifies the Active Directory realm the host is part of # # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. # # Use password server option only with security = server or if you can't # use the DNS to locate Domain Controllers # The argument list may include: # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name] # or to auto-locate the domain controller/s # password server = * ;security = domain ;passdb backend = tdbsam ;realm = MY_REALM ;password server = # --- Domain Controller Options # # Security must be set to user for domain controllers # # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. # # Domain Master specifies Samba to be the Domain Master Browser. This # allows Samba to collate browse lists between subnets. Don't use this # if you already have a Windows NT domain controller doing this job # # Domain Logons let Samba be a domain logon server for Windows workstations. # # Logon Scrpit let yuou specify a script to be run at login time on the client # You need to provide it in a share called NETLOGON # # Logon Path let you specify where user profiles are stored (UNC path) # # Various scripts can be used on a domain controller or stand-alone # machine to add or delete corresponding unix accounts # ;security = user ;passdb backend = tdbsam ;domain master = yes ;domain logons = yes # the login script name depends on the machine name ;logon script = %m.bat # the login script name depends on the unix user used ;logon script = %u.bat ;logon path = \\%L\Profiles\%u # disables profiles support by specifing an empty path ;logon path = ;add user script = /usr/sbin/useradd "%u" -n -g users ;add group script = /usr/sbin/groupadd "%g" ;add machine script = /usr/sbin/useradd -n -c "Workstation (%u)" -M -d /nohome -s /bin/false "%u" ;delete user script = /usr/sbin/userdel "%u" ;delete user from group script = /usr/sbin/userdel "%u" "%g" ;delete group script = /usr/sbin/groupdel "%g" # --- Browser Control Options # # set local master to no if you don't want Samba to become a master # browser on your network. Otherwise the normal election rules apply # # OS Level determines the precedence of this server in master browser # elections. The default value should be reasonable # # Preferred Master causes Samba to force a local browser election on startup # and gives it a slightly higher chance of winning the election ;local master =
[CentOS] Re: [Dovecot] Dovecot on CentOS5 - (login) returned error 127
Fixed, upgraded to 1.0.10 from rpm at www.atrpms.net and running now. Thank you for your support. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Dovecot on CentOS5 - (login) returned error 127
Tim Alberts wrote: Feb 21 15:41:21 cartman dovecot: pop3-login: pop3-login: error while loading shared libraries: libsepol.so.1: failed to map segment from shared object: Cannot allocate memory this is a wild guess, and should be taken with a grain or three of salt. you might try increasing kernel parameter shmmax. this is in /etc/sysctl.conf, or can be manually set for experimentation with sysctl(8) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Re: Dovecot on CentOS5 - (login) returned error 127
on 2/21/2008 3:56 PM Tim Alberts spake the following: Running CentOS Linux 5 with sendmail-procmail putting email in /var/spool/mail. I'm running pop3 only with the servers configured to authenticate with ldap (which is configured and running OK). I do have this same configuration on an older FC6 box and it works fine. I'm thinking I just need to upgrade dovecot given all the nss_ldap problems it has had, but I hate not using RPM packages and CentOS does not have upgraded packages. Hardware is Dell PowerEdge 1900 (64bit) with 2G RAM. Hopefully I'm doing something stupid and there's an easy fix for the packages and configuration I have. I'm seeing the following in the /var/log/maillog when I run dovecot. When I log in via telnet, I get the connection, but it never responds when I enter a user. Feb 21 15:41:20 cartman dovecot: Dovecot v1.0.rc15 starting up Feb 21 15:41:21 cartman dovecot: Temporary failure in creating login processes, slowing down for now Feb 21 15:41:21 cartman dovecot: pop3-login: pop3-login: error while loading shared libraries: libsepol.so.1: failed to map segment from shared object: Cannot allocate memory Feb 21 15:41:21 cartman dovecot: pop3-login: pop3-login: error while loading shared libraries: libsepol.so.1: failed to map segment from shared object: Cannot allocate memory Feb 21 15:41:21 cartman dovecot: child 4445 (login) returned error 127 Feb 21 15:41:21 cartman dovecot: child 4446 (login) returned error 127 Feb 21 15:41:21 cartman dovecot: pop3-login: pop3-login: error while loading shared libraries: libsepol.so.1: failed to map segment from shared object: Cannot allocate memory Feb 21 15:41:21 cartman dovecot: child 4447 (login) returned error 127 Feb 21 15:42:21 cartman dovecot: pop3-login: pop3-login: error while loading shared libraries: libsepol.so.1: failed to map segment from shared object: Cannot allocate memory Feb 21 15:42:21 cartman dovecot: pop3-login: pop3-login: error while loading shared libraries: libsepol.so.1: failed to map segment from shared object: Cannot allocate memory Feb 21 15:42:21 cartman dovecot: child 4465 (login) returned error 127 Feb 21 15:42:21 cartman dovecot: child 4466 (login) returned error 127 Feb 21 15:42:21 cartman dovecot: pop3-login: pop3-login: error while loading shared libraries: libsepol.so.1: failed to map segment from shared object: Cannot allocate memory Feb 21 15:42:21 cartman dovecot: child 4467 (login) returned error 127 Feb 21 15:43:21 cartman dovecot: pop3-login: pop3-login: error while loading shared libraries: libsepol.so.1: failed to map segment from shared object: Cannot allocate memory Feb 21 15:43:21 cartman last message repeated 2 times Feb 21 15:43:21 cartman dovecot: child 4469 (login) returned error 127 Feb 21 15:43:21 cartman dovecot: child 4470 (login) returned error 127 Feb 21 15:43:21 cartman dovecot: child 4471 (login) returned error 127 Feb 21 15:43:59 cartman dovecot: Killed with signal 15 Dovecot details are as follows: *> dovecot --version* 1.0.rc15 *> dovecot -n* # /etc/dovecot.conf protocols: pop3 listen: * login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/pop3-login mail_executable: /usr/libexec/dovecot/pop3 mail_plugin_dir: /usr/lib64/dovecot/pop3 pop3_client_workarounds: outlook-no-nuls oe-ns-eoh auth default: passdb: driver: pam args: dovecot userdb: driver: passwd args: blocking=yes You can download 1.0.10 rpm from www.atrpms.net -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Dovecot on CentOS5 - (login) returned error 127
Running CentOS Linux 5 with sendmail-procmail putting email in /var/spool/mail. I'm running pop3 only with the servers configured to authenticate with ldap (which is configured and running OK). I do have this same configuration on an older FC6 box and it works fine. I'm thinking I just need to upgrade dovecot given all the nss_ldap problems it has had, but I hate not using RPM packages and CentOS does not have upgraded packages. Hardware is Dell PowerEdge 1900 (64bit) with 2G RAM. Hopefully I'm doing something stupid and there's an easy fix for the packages and configuration I have. I'm seeing the following in the /var/log/maillog when I run dovecot. When I log in via telnet, I get the connection, but it never responds when I enter a user. Feb 21 15:41:20 cartman dovecot: Dovecot v1.0.rc15 starting up Feb 21 15:41:21 cartman dovecot: Temporary failure in creating login processes, slowing down for now Feb 21 15:41:21 cartman dovecot: pop3-login: pop3-login: error while loading shared libraries: libsepol.so.1: failed to map segment from shared object: Cannot allocate memory Feb 21 15:41:21 cartman dovecot: pop3-login: pop3-login: error while loading shared libraries: libsepol.so.1: failed to map segment from shared object: Cannot allocate memory Feb 21 15:41:21 cartman dovecot: child 4445 (login) returned error 127 Feb 21 15:41:21 cartman dovecot: child 4446 (login) returned error 127 Feb 21 15:41:21 cartman dovecot: pop3-login: pop3-login: error while loading shared libraries: libsepol.so.1: failed to map segment from shared object: Cannot allocate memory Feb 21 15:41:21 cartman dovecot: child 4447 (login) returned error 127 Feb 21 15:42:21 cartman dovecot: pop3-login: pop3-login: error while loading shared libraries: libsepol.so.1: failed to map segment from shared object: Cannot allocate memory Feb 21 15:42:21 cartman dovecot: pop3-login: pop3-login: error while loading shared libraries: libsepol.so.1: failed to map segment from shared object: Cannot allocate memory Feb 21 15:42:21 cartman dovecot: child 4465 (login) returned error 127 Feb 21 15:42:21 cartman dovecot: child 4466 (login) returned error 127 Feb 21 15:42:21 cartman dovecot: pop3-login: pop3-login: error while loading shared libraries: libsepol.so.1: failed to map segment from shared object: Cannot allocate memory Feb 21 15:42:21 cartman dovecot: child 4467 (login) returned error 127 Feb 21 15:43:21 cartman dovecot: pop3-login: pop3-login: error while loading shared libraries: libsepol.so.1: failed to map segment from shared object: Cannot allocate memory Feb 21 15:43:21 cartman last message repeated 2 times Feb 21 15:43:21 cartman dovecot: child 4469 (login) returned error 127 Feb 21 15:43:21 cartman dovecot: child 4470 (login) returned error 127 Feb 21 15:43:21 cartman dovecot: child 4471 (login) returned error 127 Feb 21 15:43:59 cartman dovecot: Killed with signal 15 Dovecot details are as follows: *> dovecot --version* 1.0.rc15 *> dovecot -n* # /etc/dovecot.conf protocols: pop3 listen: * login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/pop3-login mail_executable: /usr/libexec/dovecot/pop3 mail_plugin_dir: /usr/lib64/dovecot/pop3 pop3_client_workarounds: outlook-no-nuls oe-ns-eoh auth default: passdb: driver: pam args: dovecot userdb: driver: passwd args: blocking=yes ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to mount 'virtual' file systems /proc and /sys ??
On Thu, 2008-02-21 at 11:45 -0800, nate wrote:
> Robinson Tiemuqinke wrote:
>
> > Please help.
> >
>
> Looking at my BIND init scripts it calls this:
> mount --bind /proc ${ROOTDIR}/proc >/dev/null
>
>
> [EMAIL PROTECTED] init.d]# mount | grep proc
> /dev/proc on /proc type proc (rw)
> none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
> /proc on /var/named/proc type none (rw,bind)
>
>
> Not sure about the sys file system, maybe it's the
> same, maybe it's not.
For the Q posed by the OP, "man mount" gives this hint.
===
The proc file system is not associated with a special device, and
when mounting it, an arbitrary keyword, such as proc can be used instead
of a device specification. (The customary choice none is less
fortunate: the error message 'none busy' from umount can be confusing.)
===
Note also the default mounts my CentOS 4.x shows
$ mount
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
usbfs on /proc/bus/usb type usbfs (rw)
none on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
On proc, sys, pts and shm, the "none" comes from /etc/fstab, modified by
fstab-sync (see the man page for it). But IIRC from long ago, anything
that doesn't have a real device associated with it, like these, can take
any value for the fs type. Back then, sentiment was sidling towards
avoiding "none" due to the potential confusion it could cause in casual
users and the fact that hum0n eyes could more quickly scan and identify
desired items when a "rational" value appeared in place of "none".
Note that the sunrpc is different - it seems to be a result of the
loaded module sunrpc.
$ /sbin/modinfo sunrpc
filename: /lib/modules/2.6.9-67.0.4.EL/kernel/net/sunrpc/sunrpc.ko
license:GPL
vermagic: 2.6.9-67.0.4.EL 686 REGPARM 4KSTACKS gcc-3.4
depends:
Lsmod shows a use count of one, but I don't see any module using it.
However, the modinfo output in conjunction with output of this command
(I won't include the output, there's more than a line or two) makes me
think that's it's a foundation piece for RPC stuff.
$ gunzip
> nate
>
--
Bill
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to mount 'virtual' file systems /proc and /sys ??
Robinson Tiemuqinke wrote:
> Please help.
>
Looking at my BIND init scripts it calls this:
mount --bind /proc ${ROOTDIR}/proc >/dev/null
[EMAIL PROTECTED] init.d]# mount | grep proc
/dev/proc on /proc type proc (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
/proc on /var/named/proc type none (rw,bind)
Not sure about the sys file system, maybe it's the
same, maybe it's not.
nate
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
[CentOS] How to mount 'virtual' file systems /proc and /sys ??
Hello, I am setting chrooted environments with Centos/Fedora Core distros recently. packages are installed in the chrooted environment without problems. Then when it comes to /proc and /sys 'virtual'(not real hardware) file systems I got confused -- some documents say I should run 'mount -t proc none /proc; mount -t sysfs none /sys' to mount /proc and /sys, while some others say commands 'mount -t proc proc /proc; mount -t sysfs sysfs /sys' instead. I don't know what is the difference between the source device name 'none' against 'proc' and 'sysfs'. Any one can shed a light onto this? In fact, I tried command 'mount -t proc kidding /proc; mount -t sysfs kiddingAgain /sys' to successfully mounted /proc and /sys without explicit problems; access to /proc/* and /sys/* worked fine as well. Then what are the purposes of the sourceDevice field for 'virtual' file systems? Thanks. Please help. Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] system-config-display wrongly sets up Viewsonic VG730m monitor
Anne Wilson wrote: On Thursday 21 February 2008 09:56, Anne Wilson wrote: On Tuesday 19 February 2008 13:02, Johnny Hughes wrote: Maybe you are right about the driver not handling the dvi port correctly. I really didn't want to go down the route of the proprietary drivers, so maybe I will have to go back to the analogue cable. I will try your version this morning and let you know whether it helps. This is the last ditch. If it doesn't help, I'll change the cable back and re-run system-config-display. Comparing your scripts with what I'd actually put into xorg.conf, there were some extra modelins from knoppix, but the only real difference was that I'd put the dri section in. I thought it unlikely that this affect it, but I've taken it out anyway. It still is blinking. If knoppix works perfectly and does not ever blink, then I would say it is a problem with the nv Xorg driver in centos-5. If knoppix also sometimes messes up .. still might be a nv driver issue that is common to both OSes. The proprietary nvidia driver might fix that, it also adds much better 3D performance if you are using that. The modeline stuff with the CentOS-5 nv driver might also make it work correctly, if we were able to exactly define the 14 modes that I saw the monitor supported from your initial sheet. I have to admit that I am not an expert on constructing these modeline settings, but google probably can explain exactly how to construct them. Found this: http://xtiming.sourceforge.net But if the analog cable works OK, that might be the easiest option. One last thought. I did install a wireless mouse and keyboard at the same time as the dvi cable. I have a feeling that the blinking tends to happen when I move the cursor with the mouse. Is it possible that there is interference from the mouse? I have never heard of this happening before, but it would be theoretically possible, though not probable IMHO. If you hook up a normal mouse and it goes away ... maybe so, that should be a fairly easy test. Thanks, Johnny Hughes signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] yum-proxy?
Les Mikesell wrote: Lorenzo Quatrini wrote: I've been using Debian for a few years, and there was one nifty little app that made installing and updating so much easier: apt-proxy. Most of the time, I'm taking care of small LANs with an average of five client PCs. But this is a very remote place in South France, so most villages only have 512 kbps DSL. One major update for openoffice.org-*, and I have to wait the whole day for updating each machine (unless I scp -r /var/cache/yum from machine to machine, but that's another story). I'm currently testing an "intermediate" solution: creating a local Yum repository. I have [base], which consists of all the 5.1 RPMS copied over from the DVD. Then [updates], which I'm currently rsyncing from a remote mirror. And I think I'll do something similar with [extra], which only leaves [rpmforge] (but I won't cache that :oD). Not a very satisfying solution, since for example I'm currently installing XFCE as only desktop environment, and I have nevertheless to download every GNOME- and KDE-related update. A message to the developers: yum-proxy would be a much-needed addition to Yum, in my humble opinion. I don't have the technical skills to develop such a thing, but maybe one of you has (Daniel, do you read this? :oD) I'm curious about your comments on this. Cheers, Niki I also need such a thing... I'm on the process to have a friend of mine write a patch to http-replicator so that it can work as a proxy for rpm files. Stay tuned, shortly, I hope, I'll have some news. If you are in a location where a caching proxy is useful, wouldn't it be nicer to configure a squid to cache large files and teach yum to behave better in the presence of proxies (i.e. not use a mirrorlist or at least always pick the same server as the first choice from the same location) instead of having ad-hoc per-distribution per-version solutions that won't be of any other use? Personally, if I was at such a location (where more that 1 or 2 machines needed updates), instead of trying to change anything, I would just rsync the branches of the centos tree I needed down to a web server and have a local mirror. It takes 5 minutes to setup, and you can do new installs, updates, etc. going forward from the local mirror. signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] system-config-display wrongly sets up Viewsonic VG730m monitor
On Thursday 21 February 2008 09:56, Anne Wilson wrote: > On Tuesday 19 February 2008 13:02, Johnny Hughes wrote: > > You say that you bought a digital lead ... meaning I guess that you are > > using a different PORT on your video card and monitor. It is possible > > that he standard "nv" driver does not support that port on your video > > card and that you will need to instead download the proprietary drivers > > from nvidia's website to get that port to function. Regardless of which > > driver and cable you use, the resolution/freq of the screen is going to > > be the same ... why not just use the old cable :D > > Hi, Johnny. Sorry for the delay in answering, but I was trying to make > sure that I had a fair amount of time to work with the server. > > Before I read your message I had the bright idea of seeing what knoppix > thought about the monitor. The result was surprising. Attached is what it > reported. I fed that info into xorg.conf and hoped. Unfortunately I am > still seeing the blink from time to time, though. > > Maybe you are right about the driver not handling the dvi port correctly. > I really didn't want to go down the route of the proprietary drivers, so > maybe I will have to go back to the analogue cable. > > I will try your version this morning and let you know whether it helps. > This is the last ditch. If it doesn't help, I'll change the cable back and > re-run system-config-display. > Comparing your scripts with what I'd actually put into xorg.conf, there were some extra modelins from knoppix, but the only real difference was that I'd put the dri section in. I thought it unlikely that this affect it, but I've taken it out anyway. It still is blinking. One last thought. I did install a wireless mouse and keyboard at the same time as the dvi cable. I have a feeling that the blinking tends to happen when I move the cursor with the mouse. Is it possible that there is interference from the mouse? Anne ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] system-config-display wrongly sets up Viewsonic VG730m monitor
On Tuesday 19 February 2008 13:02, Johnny Hughes wrote: > > You say that you bought a digital lead ... meaning I guess that you are > using a different PORT on your video card and monitor. It is possible > that he standard "nv" driver does not support that port on your video > card and that you will need to instead download the proprietary drivers > from nvidia's website to get that port to function. Regardless of which > driver and cable you use, the resolution/freq of the screen is going to > be the same ... why not just use the old cable :D > Hi, Johnny. Sorry for the delay in answering, but I was trying to make sure that I had a fair amount of time to work with the server. Before I read your message I had the bright idea of seeing what knoppix thought about the monitor. The result was surprising. Attached is what it reported. I fed that info into xorg.conf and hoped. Unfortunately I am still seeing the blink from time to time, though. Maybe you are right about the driver not handling the dvi port correctly. I really didn't want to go down the route of the proprietary drivers, so maybe I will have to go back to the analogue cable. I will try your version this morning and let you know whether it helps. This is the last ditch. If it doesn't help, I'll change the cable back and re-run system-config-display. Thanks again Anne # Auto-generated by KNOPPIX mkxf86config Section "Monitor" Identifier "Monitor0" Option "DPMS" "true" VendorName "VSC" ModelName "VSC951e" HorizSync 30 - 82 # DDC-probed VertRefresh 50 - 75 # DDC-probed # These are the DDC-probed settings reported by your monitor. # 1280x1024, 75.0Hz; hfreq=79.98, vfreq=75.03 ModeLine "1280x1024"135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync # 1152x864, 75.0Hz; hfreq=67.50, vfreq=75.00 ModeLine "1152x864" 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync # 1024x768, 75.0Hz; hfreq=60.02, vfreq=75.03 ModeLine "1024x768" 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync # 1024x768, 70.0Hz; hfreq=56.48, vfreq=70.07 ModeLine "1024x768" 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync # 800x600, 75.0Hz; hfreq=46.88, vfreq=75.00 ModeLine "800x600" 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync # 800x600, 72.0Hz; hfreq=48.08, vfreq=72.19 ModeLine "800x600" 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync # 800x600, 60.0Hz; hfreq=37.88, vfreq=60.32 ModeLine "800x600" 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync # 640x480, 75.0Hz; hfreq=37.50, vfreq=75.00 ModeLine "640x480" 31.50 640 656 720 840 480 481 484 500 -hsync -vsync # 640x480, 72.0Hz; hfreq=37.86, vfreq=72.81 ModeLine "640x480" 31.50 640 656 696 816 480 481 484 504 -hsync -vsync # 640x480, 60.0Hz; hfreq=31.47, vfreq=59.94 ModeLine "640x480" 25.17 640 648 744 784 480 482 484 509 -hsync -vsync # Extended modelines with GTF timings # 640x480 @ 100.00 Hz (GTF) hsync: 50.90 kHz; pclk: 43.16 MHz ModeLine "640x480" 43.16 640 680 744 848 480 481 484 509 -HSync +Vsync # 768x576 @ 60.00 Hz (GTF) hsync: 35.82 kHz; pclk: 34.96 MHz ModeLine "768x576" 34.96 768 792 872 976 576 577 580 597 -HSync +Vsync # 768x576 @ 72.00 Hz (GTF) hsync: 43.27 kHz; pclk: 42.93 MHz ModeLine "768x576" 42.93 768 800 880 992 576 577 580 601 -HSync +Vsync # 768x576 @ 75.00 Hz (GTF) hsync: 45.15 kHz; pclk: 45.51 MHz ModeLine "768x576" 45.51 768 808 888 1008 576 577 580 602 -HSync +Vsync # 768x576 @ 85.00 Hz (GTF) hsync: 51.42 kHz; pclk: 51.84 MHz ModeLine "768x576" 51.84 768 808 888 1008 576 577 580 605 -HSync +Vsync # 768x576 @ 100.00 Hz (GTF) hsync: 61.10 kHz; pclk: 62.57 MHz ModeLine "768x576" 62.57 768 816 896 1024 576 577 580 611 -HSync +Vsync # 800x600 @ 100.00 Hz (GTF) hsync: 63.60 kHz; pclk: 68.18 MHz ModeLine "800x600" 68.18 800 848 936 1072 600 601 604 636 -HSync +Vsync # 1024x768 @ 100.00 Hz (GTF) hsync: 81.40 kHz; pclk: 113.31 MHz ModeLine "1024x768" 113.31 1024 1096 1208 1392 768 769 772 814 -HSync +Vsync # 1152x864 @ 60.00 Hz (GTF) hsync: 53.70 kHz; pclk: 81.62 MHz ModeLine "1152x864" 81.62 1152 1216 1336 1520 864 865 868 895 -HSync +Vsync # 1152x864 @ 85.00 Hz (GTF) hsync: 77.10 kHz; pclk: 119.65 MHz ModeLine "1152x864" 119.65 1152 1224 1352 1552 864 865 868 907 -HSync +Vsync # 1152x864 @ 100.00 Hz (GTF) hsync: 91.50 kHz; pclk: 143.47 MHz ModeLine "1152x864" 143.47 1152 1232 1360 1568 864 865 868 915 -HSync +Vsync # 1280x960 @ 72.00 Hz (GTF) hsync: 72.07 kHz;
[CentOS] Is Gnome in CentOS 5 ready for nfsv4?
Hello, all my data are hosted by a server and exported with nfsv4. For example if a user logs in on a client, /home and /data are exported with nfsv4 and autofs. Now if the user delete some files, the trashcan under gnome doesn't change its status nor doesn't show the deleted files if opening the trashcan window. Also the user isn't able to copy or move files between the exported directories with nautilus, the error message is talking about "different file systems". Is this a gnome-vfs2 bug in gnome-2.16? regards Olaf ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
