[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: kdeinit_wrapper can't connect to kdeinit
From:       Waldo Bastian <bastian () kde ! org>
Date:       2000-08-29 4:08:02
[Download RAW message or body]

On Mon, 28 Aug 2000, Michael Matz wrote:
> Hi,
>
> On Mon, 28 Aug 2000, Waldo Bastian wrote:
> > > Yes, seems to be a 2.4 problem. Is there any reason why this patch
> > > isn't in cvs yet?
> >
> > It's a kernel bug. I'm about to change this stuff a bit because I don't
> > like these sym-links at all. I will add two resource types "tmp" and
> > "socket" that resolve to $KDEHOME/tmp-<hostname> and
> > $KDEHOME/socket-<hostname>.
>
> What is the reason for defaulting to $KDEHOME instead of /tmp/kde-<user>

Well, I would like to use /tmp/kde-<username> but I can't guarantee that I 
can create it. So the next best thing is to use $KDEHOME/tmp-<hostname> and 
make that a link to preferably /tmp/kde-<username> or /tmp/<something else> 
if I can't create /tmp/kde-<username>.

> (or sth. like that) (at least for the socket resource), if our
> recommendation is anyway to make that symlinks to /tmp? If KDEHOME is the
> default, this means work for socket-less homedirs (and then usually for a
> huge number of users), but if /tmp this means no more work work users with
> normal home-dirs.  With /tmp it's the same. Traditionally /tmp is the path
> for temporary files; _all_ of them. 

> I don't see the point of having a tmp
> directory in the home-dir, esp. thinking about quotas on $HOME, while
> usually there is no quota on /tmp. So this would mean even more work for
> most installations with a large user base.
>
> > I will add a program that sets up the symlinks to /tmp which you can add
> > to your startkde script.
>
> So defaulting to /tmp means also less work for you ;)

Look at how kdeinit currently handles it socket... 

Cheers,
Waldo
-- 
KDE/Linux, made for people, made by people.

[prev in list] [next in list] [prev in thread] [next in thread]