Bug#50859: xfs Bug #50859: use start-stop-daemon --chuid ?

2008-06-06 Thread Petter Reinholdtsen
[Julien Cristau] So how about creating a dedicated user for xfs, and moving logs to a /var/log/xfs/ directory where this user can write? Please send the messages to syslog instead of a separate log file. It make it easier to track issues with xfs across several machines, and solve the problem

Bug#50859: xfs Bug #50859: use start-stop-daemon --chuid ?

2008-06-06 Thread Julien Cristau
On Fri, May 16, 2008 at 21:52:58 +0200, Sven Joachim wrote: On 2008-05-16 13:07 +0200, Julien Cristau wrote: On Fri, May 16, 2008 at 08:16:20 +0200, Sven Joachim wrote: Just FYI, I've been running xfs with this patch for the last few days and don't have any problems. Could this be

Bug#50859: xfs Bug #50859: use start-stop-daemon --chuid ?

2008-05-17 Thread Sven Joachim
On 2008-05-16 23:43 +0200, Petter Reinholdtsen wrote: [Sven Joachim] Not at all, good catch. I just didn't know it even has a log file. How about compiling with -DUSE_SYSLOG? I must admit, I would prefer xfs logging to syslog. When debugging the segfault in #148650, the first place I

Bug#50859: xfs Bug #50859: use start-stop-daemon --chuid ?

2008-05-16 Thread Sven Joachim
On 2008-05-12 08:15 +0200, Petter Reinholdtsen wrote: Ah, right. This work better. Now the xfs process is running as user nobody. This is the patch. diff -ur xfs-1.0.6/debian/xfs.init xfs-1.0.6.pere/debian/xfs.init --- xfs-1.0.6/debian/xfs.init 2008-05-12 08:13:32.0 +0200 +++

Bug#50859: xfs Bug #50859: use start-stop-daemon --chuid ?

2008-05-16 Thread Petter Reinholdtsen
[Sven Joachim] Just FYI, I've been running xfs with this patch for the last few days and don't have any problems. Could this be uploaded to unstable to get xfs back into testing? I can NMU if the maintainers do not have time to work on in soon. Happy hacking, -- Petter Reinholdtsen --

Bug#50859: xfs Bug #50859: use start-stop-daemon --chuid ?

2008-05-16 Thread Julien Cristau
On Fri, May 16, 2008 at 08:16:20 +0200, Sven Joachim wrote: Just FYI, I've been running xfs with this patch for the last few days and don't have any problems. Could this be uploaded to unstable to get xfs back into testing? One question though: how can xfs reopen its log file when running

Bug#50859: xfs Bug #50859: use start-stop-daemon --chuid ?

2008-05-16 Thread Sven Joachim
On 2008-05-16 13:07 +0200, Julien Cristau wrote: On Fri, May 16, 2008 at 08:16:20 +0200, Sven Joachim wrote: Just FYI, I've been running xfs with this patch for the last few days and don't have any problems. Could this be uploaded to unstable to get xfs back into testing? One question

Bug#50859: xfs Bug #50859: use start-stop-daemon --chuid ?

2008-05-16 Thread Petter Reinholdtsen
[Sven Joachim] Not at all, good catch. I just didn't know it even has a log file. How about compiling with -DUSE_SYSLOG? I must admit, I would prefer xfs logging to syslog. When debugging the segfault in #148650, the first place I looked was /var/log/syslog. When Nothing showed up there, I

Bug#50859: xfs Bug #50859: use start-stop-daemon --chuid ?

2008-05-12 Thread Petter Reinholdtsen
tags 50859 + patch thanks [Julien Cristau] Add -user nobody -droppriv to the xfs command line arguments. Ah, right. This work better. Now the xfs process is running as user nobody. This is the patch. diff -ur xfs-1.0.6/debian/xfs.init xfs-1.0.6.pere/debian/xfs.init ---

Bug#50859: xfs Bug #50859: use start-stop-daemon --chuid ?

2008-05-11 Thread Drew Parsons
Julien Cristau wrote: Yes, I think we shouldn't have xfs running as root in lenny. Can't this bug now be dealt with simply by using start-stop-daemon --chuid (not sure which user. Will nobody do ? Or daemon? If not xfs) ? Or is there some subtlety preventing this from solving the problem?

Bug#50859: xfs Bug #50859: use start-stop-daemon --chuid ?

2008-05-11 Thread Julien Cristau
On Mon, May 12, 2008 at 00:42:10 +1000, Drew Parsons wrote: Julien Cristau wrote: Yes, I think we shouldn't have xfs running as root in lenny. Can't this bug now be dealt with simply by using start-stop-daemon --chuid (not sure which user. Will nobody do ? Or daemon? If not xfs) ? Or

Bug#50859: xfs Bug #50859: use start-stop-daemon --chuid ?

2008-05-11 Thread Petter Reinholdtsen
[Julien Cristau] You'll need to add a new system user in postinst, too. Why must it have a new system user? I would expect nobody to be a user with no privileges, and thus perfectly usable for this purpose? Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL

Bug#50859: xfs Bug #50859: use start-stop-daemon --chuid ?

2008-05-11 Thread Julien Cristau
On Sun, May 11, 2008 at 17:14:39 +0200, Petter Reinholdtsen wrote: [Julien Cristau] You'll need to add a new system user in postinst, too. Why must it have a new system user? I would expect nobody to be a user with no privileges, and thus perfectly usable for this purpose? If you tested

Bug#50859: xfs Bug #50859: use start-stop-daemon --chuid ?

2008-05-11 Thread Petter Reinholdtsen
[Julien Cristau] If you tested that and are confident that it works, sure. I never used xfs myself, so I don't know. I am quite confident that user nobody will have the required acces to the font files. But I just tested modifying /etc/init.d/xfs to include --chuid nobody, and it fail to

Bug#50859: xfs Bug #50859: use start-stop-daemon --chuid ?

2008-05-11 Thread Julien Cristau
On Mon, May 12, 2008 at 00:22:29 +0200, Petter Reinholdtsen wrote: [Julien Cristau] If you tested that and are confident that it works, sure. I never used xfs myself, so I don't know. I am quite confident that user nobody will have the required acces to the font files. But I just