Re: [Cooker] Problem with XFree86-4.0.2-2mdk
If you take a look in /var/log/syslog when you try to start xfs you might find something like: Jan 6 18:21:05 stefan xfs: xfs startup succeeded Jan 6 18:21:05 stefan xfs: process-id file /var/run/xfs.pid cannot be opened Jan 6 18:21:05 stefan xfs: can't create/lock pid file Maybe it has something to do with it... "J . A . Magallon" wrote: On 2001.01.07 Robin Cook wrote: Hello, I updated to the XFree86-4.0.2-2mdk and now X won't start. It comes back with something about not being able to find the default font fixed. Look at /etc/rc.d/init.d/xfs, search lines like ... su xfs -c xfs -port -1 and change to ... xfs -droppriv -port -1 (ie, delete the 'su xfs' part, and add a -droppriv). Don't know why, but this script seems to have problems with 'su'.. -- J.A. Magallon $ cd pub mailto:[EMAIL PROTECTED] $ more beer Linux werewolf 2.4.0-ac2 #6 SMP Sat Jan 6 01:38:26 CET 2001 i686
Re: [Cooker] Problem with XFree86-4.0.2-2mdk
from the quill of Stefan van der Eijk [EMAIL PROTECTED] on scroll [EMAIL PROTECTED] If you take a look in /var/log/syslog when you try to start xfs you might find something like: Jan 6 18:21:05 stefan xfs: xfs startup succeeded Jan 6 18:21:05 stefan xfs: process-id file /var/run/xfs.pid cannot be opened Jan 6 18:21:05 stefan xfs: can't create/lock pid file Maybe it has something to do with it... It has everything to do with it. The whole idea of suing to xfs before starting xfs is flawed for two reasons. First, xfs' shell in /etc/passwd is /bin/false by default and second, as you note above, once the process is su'd to xfs, it cannot access /var/run/xfs.pid. Is this su'ing to xfs something new with the most recent release of XFree86? b. -- Brian J. Murrell
Re: [Cooker] Problem with XFree86-4.0.2-2mdk
"J . A . Magallon" [EMAIL PROTECTED] writes: On 2001.01.07 Robin Cook wrote: Hello, I updated to the XFree86-4.0.2-2mdk and now X won't start. It comes back with something about not being able to find the default font fixed. Look at /etc/rc.d/init.d/xfs, search lines like ... su xfs -c xfs -port -1 and change to ... xfs -droppriv -port -1 (ie, delete the 'su xfs' part, and add a -droppriv). Don't know why, but this script seems to have problems with 'su'.. ? I don't need droppriv to make it work. here's mine: daemon xfs -port -1 -daemon -user xfs -- Guillaume Cottenceau - http://us.mandrakesoft.com/~gc/
Re: [Cooker] Problem with XFree86-4.0.2-2mdk
Guillaume Cottenceau wrote: I don't need droppriv to make it work. here's mine: daemon xfs -port -1 -daemon -user xfs -droppriv causes xfs to run as user xfs -user allows you to specify the user to run as They are basically the same. If you su to xfs before running xfs, you can't write to /var/run. John
Re: [Cooker] Problem with XFree86-4.0.2-2mdk
Of course you don't need droppriv, but you want it for security reasons. -- Brian I don't need droppriv to make it work. here's mine: daemon xfs -port -1 -daemon -user xfs
Re: [Cooker] Problem with XFree86-4.0.2-2mdk
On 2001.01.07 [EMAIL PROTECTED] wrote: Of course you don't need droppriv, but you want it for security reasons. -- Brian I don't need droppriv to make it work. here's mine: daemon xfs -port -1 -daemon -user xfs Right. The thing I still do not understand is why the hell if there is a way to do the 'run as user xfs' directly from xfs, anybody thought on that mess of the 'su xfs 'c xfs...'. -- J.A. Magallon $ cd pub mailto:[EMAIL PROTECTED] $ more beer Linux werewolf 2.4.0-ac3 #2 SMP Sun Jan 7 02:13:37 CET 2001 i686
Re: [Cooker] Problem with XFree86-4.0.2-2mdk
Guillaume Cottenceau wrote: "J . A . Magallon" [EMAIL PROTECTED] writes: ... xfs -droppriv -port -1 I don't need droppriv to make it work. But perhaps you need droppriv to make it *safe*? -- A computer scientist is someone who, when told to "Go to Hell," sees the "go to," rather than the destination, as harmful. -- Dr. Roger M. Firestone, [EMAIL PROTECTED]
[Cooker] Problem with XFree86-4.0.2-2mdk
Hello, I updated to the XFree86-4.0.2-2mdk and now X won't start. It comes back with something about not being able to find the default font fixed. -- Best regards, Robin mailto:[EMAIL PROTECTED]
Re: [Cooker] Problem with XFree86-4.0.2-2mdk
On 2001.01.07 Robin Cook wrote: Hello, I updated to the XFree86-4.0.2-2mdk and now X won't start. It comes back with something about not being able to find the default font fixed. Look at /etc/rc.d/init.d/xfs, search lines like ... su xfs -c xfs -port -1 and change to ... xfs -droppriv -port -1 (ie, delete the 'su xfs' part, and add a -droppriv). Don't know why, but this script seems to have problems with 'su'.. -- J.A. Magallon $ cd pub mailto:[EMAIL PROTECTED] $ more beer Linux werewolf 2.4.0-ac2 #6 SMP Sat Jan 6 01:38:26 CET 2001 i686
Re: [Cooker] Problem with XFree86-4.0.2-2mdk
Hello, I updated to the XFree86-4.0.2-2mdk and now X won't start. It comes back with something about not being able to find the default font fixed. it's the xfs-server which isn't running and without that X won't run(not totally true but for mere mortals it is).I have the same problem. -- Best regards, Robin mailto:[EMAIL PROTECTED]
Re[2]: [Cooker] Problem with XFree86-4.0.2-2mdk
Hello andre, The Xfs server was running until I try to start x but then it dies. Saturday, January 06, 2001, 6:29:00 PM, you wrote: Hello, I updated to the XFree86-4.0.2-2mdk and now X won't start. It comes back with something about not being able to find the default font fixed. a it's the xfs-server which isn't running and without that X won't run(not totally true but for mere mortals it is).I have the same problem. -- Best regards, Robin mailto:[EMAIL PROTECTED] -- Best regards, Robinmailto:[EMAIL PROTECTED]
Re: [Cooker] Problem with XFree86-4.0.2-2mdk
the only way i could run xfs server was to change this line in etc/rc.d/init.d/xfs. #original daemon --check xfs su xfs -c \"xfs -port -1 -daemon\" -s /bin/sh #replaced daemon xfs -droppriv -port -1 -daemon On Sunday 07 January 2001 00:53, you wrote: On 2001.01.07 Robin Cook wrote: Hello, I updated to the XFree86-4.0.2-2mdk and now X won't start. It comes back with something about not being able to find the default font fixed. Look at /etc/rc.d/init.d/xfs, search lines like ... su xfs -c xfs -port -1 and change to ... xfs -droppriv -port -1 (ie, delete the 'su xfs' part, and add a -droppriv). Don't know why, but this script seems to have problems with 'su'..
