On Saturday, December 11, 2010 02:55:47 am Basil Chupin wrote:

I came across a file in her /home directory which showed up as named "!gfs" or "!gvs" or something similar.

As root I could not access it nor delete it: "Access denied" (it had zero bytes for size, anyway).

It is link to /home/user/.gvfs directory. Look on the web for "root can't delete gvfs". It is gvfs-fuse mount point that can access only user of that file system. The reason is privacy and you can imagine that is design decision, not a bug, but in any case it is something that acts contrary to common sense in Unix, where system admin can access any point of computer. Is it good or not, I can't say. It puts user above system admin for some stuff, which is IMHO, no a good idea. On the other hand, it protects user stuff from bad sysadmins that would like to peek where they should not. When first time appeared many considered that as a bug, like in this report: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/225361 I use KDE and I have it. I'm not sure is the reason few GTk applications I use, or something else. http://en.wikipedia.org/wiki/GVFS http://fedoraproject.org/wiki/Features/Gvfs -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On 12/12/10 05:05, Basil Chupin wrote:

On 11/12/2010 22:57, Rajko M. wrote:

...

On Saturday, December 11, 2010 02:55:47 am Basil Chupin wrote:

...

I came across a file in her /home directory which showed up as named "!gfs" or "!gvs" or something similar.

As root I could not access it nor delete it: "Access denied" (it had zero bytes for size, anyway). It is link to /home/user/.gvfs directory. Look on the web for "root can't delete gvfs". It is gvfs-fuse mount point that can access only user of that file system. The reason is privacy and you can imagine that is design decision, not a bug, but in any case it is something that acts contrary to common sense in Unix, where system admin can access any point of computer.

Ah, many thanks for this Rajko. Next time I come across this I won't bother agonising about how to delete it :-) .

BC

When I first saw the message I was puzzled, a little bit of research told me it was a mounted filesystem so I umounted it. Others since then got worried and I explained it. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

* Donn Washburn [12-11-10 09:11]:

...

* Donn Washburn [12-10-10 23:05]: Nothing wrong here. It worked correctly until I did and "zypper dup". Now it just fails I removed it with "rpm -e tvtime". Reloaded it "zypper in tvtime". Went back to X and from a xterm called tvtime.

Ok, now you have started a process, tvtime.

It came up with a blue image and failed to work. Closed it. I then tried it from a desktop icon - it failed./crashed without a bootsplash or image. Again back to the xterm - It showed in the following error.

~> tvtime Running tvtime 1.0.2. Reading configuration from /etc/tvtime/tvtime.xml Reading configuration from /home/donn/.tvtime/tvtime.xml Cannot run two instances of tvtime with the same configuration.

The process, tvtime, that you closed failed to close.

~> locate tvtime.xml /etc/tvtime/tvtime.xml /usr/share/doc/packages/tvtime/html/default.tvtime.xml /home/donn/.tvtime/tvtime.xml /usr/share/man/de/man5/tvtime.xml.5.gz /usr/share/man/es/man5/tvtime.xml.5.gz /usr/share/man/man5/tvtime.xml.5.gz

again, this is just a listing of directories/files on your system.

~> ps ax | grep tvtime 16292 ? D 0:03 [tvtime]

~> kill -9 116392 16292 ? D 0:03 [tvtime]

~> ps ax | grep tvtime 16292 ? D 0:03 [tvtime]

As root - in a xterm - It comes up but can not be killed using the image "X" or Close as root --> ps ax | grep tvtime 16292 ? D 0:03 [tvtime] 16486 ? D< 0:00 tvtime

You now have two instances (processes) of tvtime, both in state "D". from the little used man pages which explain the results you received above: <quote> PROCESS STATE CODES Here are the different values that the s, stat and state output specifiers (header "STAT" or "S") will display to describe the state of a process. D Uninterruptible sleep (usually IO) R Running or runnable (on run queue) S Interruptible sleep (waiting for an event to complete) T Stopped, either by a job control signal or because it is being traced. W paging (not valid since the 2.6.xx kernel) X dead (should never be seen) Z Defunct ("zombie") process, terminated but not reaped by its parent. </quote>

From my limited experiennce, I believe you have a "hung" process which cannot be cleared w/o dropping to runlevel 1 or a reboot. (I may be wrong here. Someone need to clarify.)

I would file a bug report against this version of tvtime and return to the previous version. zypper rm tvtime zypper se -s --match-exact tvtime zypper in tvtime- SuSEconfig;ldconfig zypper al -r <repo of new version tvtime> tvtime to check for when a newer version of tvtime becomes available: crontab -e MAILTO= 44 1 * * * zypper se -s --match-exact tvtime when a newer version becomes available, zypper rl tvtime will remove the lock and your normal update sequence will install the newer version. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org