Re: KDE and KDM issues still

2002-09-20 Thread Jonathan Chen

On Fri, Sep 20, 2002 at 02:52:59AM -0400, James Dean wrote:

 ttyv8   /usr/local/bin/kdmxterm   on  secure
 
 I keep getting these errors messages in my logs:
 Sep  7 13:00:28 bsdguru kdm_config[12241]: Unknown command line option 
 'ttyv8'
 Sep  7 13:00:28 bsdguru kdm[12243]: Can't lock pid file /var/run/kdm.pid, 
 anothe
 r xdm is running (pid 281)

You need to change the ttyv8 line to:

ttyv8   /usr/local/bin/kdm -nodaemon xterm   on  secure

Your current setting is trying to spawn multiple copies of kdm, all of
which (aside from the first one) are failing because the first one is
running. The Unknown command line option, you can't do anything
about, so just ignore it.
-- 
Jonathan Chen [EMAIL PROTECTED]
--
 A person should be able to do a small bit of everything,
specialisation is for insects

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: KDE and KDM issues still

2002-09-20 Thread Kenneth Culver

On Friday 20 September 2002 04:22 am, Jonathan Chen wrote:
 On Fri, Sep 20, 2002 at 02:52:59AM -0400, James Dean wrote:
  ttyv8   /usr/local/bin/kdmxterm   on  secure
 
  I keep getting these errors messages in my logs:
  Sep  7 13:00:28 bsdguru kdm_config[12241]: Unknown command line option
  'ttyv8'
  Sep  7 13:00:28 bsdguru kdm[12243]: Can't lock pid file /var/run/kdm.pid,
  anothe
  r xdm is running (pid 281)

 You need to change the ttyv8 line to:

   ttyv8   /usr/local/bin/kdm -nodaemon xterm   on  secure

 Your current setting is trying to spawn multiple copies of kdm, all of
 which (aside from the first one) are failing because the first one is
 running. The Unknown command line option, you can't do anything
 about, so just ignore it.

Do you have any idea why when I start kde from kdm, kdesu won't work? Or why I 
keep getting this: 

Sep 20 08:56:49 ken kdm[159]: Abnormal helper termination, code 0, signal 17

I can't find solutions to either problem.

Ken

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: KDE and KDM issues still

2002-09-20 Thread Adrian Mugnolo

Hi,

 ttyv8   /usr/local/bin/kdmxterm   on  secure

You're missing the -nodaemon option here.  It should read:

ttyv8   /usr/local/bin/kdm -nodaemon  xterm   on  secure

Please note that if you're running:

kdebase-3.0_1   Base modules for the KDE integrated X11 desktop
kdelibs-3.0_1   Libraries for KDE

As packaged with RELEASE-4.6.2, you should start kdm from somewhere
else.  Starting it from init(1) brings a problem with konsole.  I use
this in rc.local:

( sleep 45 ; /usr/local/bin/kdm ) 
echo -n ' kdm'

[The 45 second sleep depends on how much are you starting from
/usr/local/etc/rc.d -- this should happen after all you plain text
console(4) getty's start.]

 I keep getting these errors messages in my logs:  Sep 7 13:00:28
 bsdguru kdm_config[12241]: Unknown command line option 'ttyv8'

Kdm doesn't like the tty argument as passed from init(1).  Here's a
patch for that problem:

Index: init.c
===
RCS file: /home/ncvs/src/sbin/init/init.c,v
retrieving revision 1.38.2.8
diff -u -p -r1.38.2.8 init.c
--- init.c  2001/10/22 11:27:32 1.38.2.8
+++ init.c  2002/09/20 17:43:36
@@ -1027,8 +1027,13 @@ setupargv(sp, typ)
free(sp-se_getty_argv_space);
free(sp-se_getty_argv);
}
-   sp-se_getty = malloc(strlen(typ-ty_getty) + strlen(typ-ty_name) + 2);
-   (void) sprintf(sp-se_getty, %s %s, typ-ty_getty, typ-ty_name);
+   if (strstr(typ-ty_getty, kdm)) {
+   /* kdm doesn't expect a tty name */
+   sp-se_getty = strdup(typ-ty_getty);
+   } else {
+   sp-se_getty = malloc(strlen(typ-ty_getty) + strlen(typ-ty_name) + 
+2);
+   (void) sprintf(sp-se_getty, %s %s, typ-ty_getty, typ-ty_name);
+   }
sp-se_getty_argv_space = strdup(sp-se_getty);
sp-se_getty_argv = construct_argv(sp-se_getty_argv_space);
if (sp-se_getty_argv == 0) {

IMO there should be an elegant way to let init(1) know which programs
expect this argument, possibly with an option in /etc/ttys, or have a
wrapper script around kdm to avoid this.

HTH

Regards

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message