Re: LUG: gconfd problem - Wed, 13 May 2009 19:47:23 -0400

Subject : Re: LUG: gconfd problem

From : Alexander Ray <alexjray.ncsu@gmail.[redacted]>

Date : Wed, 13 May 2009 19:47:23 -0400

Hey, any LUGer's out there wanna check and sound off on this:
Are you're ~/.gconf and ~/.gconfd symbolic links in your AFS home?

I know me (Alex R) and Alex K both have symlinks to something in .realmfiles/

On Wed, May 13, 2009 at 4:51 PM, Jack Neely <jjneely@ncsu.[redacted]> wrote:
> On Wed, May 13, 2009 at 04:47:38PM -0400, Alexander Ray wrote:
>> My .gconf and .gconfd are symlinks and their timestamps reads: Sep 16 2008
>
> Weird. �I've never setup anything to symlink around ~/.gconf and
> ~/.gconfd. �Gconf has been...mostly....stable in AFS since the locking
> parts were moved to live in /tmp.
>
> Jack
>
>>
>> On Wed, May 13, 2009 at 4:44 PM, Jack Neely <jjneely@ncsu.[redacted]> wrote:
>> > On Wed, May 13, 2009 at 04:29:23PM -0400, Alexander Ray wrote:
>> >> Hey guys,
>> >>
>> >> I got a really interesting case where someone's .gconf and .gconfd
>> >> files in their AFS space are actually NOT symbolically linked to
>> >> .realmtools/@sys files.
>> >>
>> >> 1) has anyone else run into this sort of thing before?
>> >> and
>> >> 2) does anyone have enough experience with these to bring these issues
>> >> to a swift resolution?
>> >>
>> >> Thanks,
>> >> Alex
>> >
>> > When were the .gconf* directories symlinked?
>> >
>> > Jack
>> > --
>> > Jack Neely <jjneely@ncsu.[redacted]>
>> > Linux Czar, OIT Campus Linux Services
>> > Office of Information Technology, NC State University
>> > GPG Fingerprint: 1917 5AC1 E828 9337 7AA4 �EA6B 213B 765F 3B6A 5B89
>> >
>>
>
> --
> Jack Neely <jjneely@ncsu.[redacted]>
> Linux Czar, OIT Campus Linux Services
> Office of Information Technology, NC State University
> GPG Fingerprint: 1917 5AC1 E828 9337 7AA4 �EA6B 213B 765F 3B6A 5B89
>

Replies :

Re: LUG: gconfd problem