On Thu, Oct 11, 2007 at 12:10:04PM +0100, Pedro Celestino dos Reis Rodrigues
wrote:
Automounted homes over nfs4 with sec=krb5
Start a session on the nfs client and let the user ticked (used to grant the
nfs access) expire
After this the user can not access is home (as should be expected)
On Mon, Sep 24, 2007 at 04:29:02PM -0700, David Liontooth wrote:
Hi Neil,
Thanks for looking.
I didn't see an answer to this mail; was the problem forgotten, or was it
resolved?
/* Steinar */
--
Homepage: http://www.sesse.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
reassign 446383 linux-image-2.6.22-1-k7
thanks
On Fri, Oct 12, 2007 at 01:33:27PM -0700, Bardia Fallah Behabadi wrote:
the root user and group were not being displayed properly in the mounts
(instead showing as nobody/nogroup) and on the mounting machine as root
i couldn't modify any files
On Mon, Oct 08, 2007 at 03:41:21PM -0400, Roberto C. Sánchez wrote:
Given the great abundance of revision control systems already packaged
for Debian, what is the point of adding another?
I don't see the relevance of this argument, really, but if you really think
it's a problem: What if someone
On Sun, Sep 30, 2007 at 08:32:14PM +0200, Ola Lundqvist wrote:
But how did you get it work when it FTBFS? Interested...
I cp-ed the .so in to the right place. The FTBFS was in some man page stuff I
didn't care much about.
/* Steinar */
--
Homepage: http://www.sesse.net/
--
To UNSUBSCRIBE,
On Sun, Sep 30, 2007 at 01:13:56PM +0200, Julian Andres Klode wrote:
Description : open source implementation of VMware Tools
Provides functions like file transfers between host and guest,
and improved performance.
You might want to specify a bit what this works with. Does it work only
Package: vnc4server
Version: 4.1.1+X4.3.0-21
Severity: grave
Justification: renders package unusable
Hi,
Since I upgraded X.org I can no longer press keys remotely. If I do so,
the X server crashes with:
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x7e) [0x80c644e]
1: [0xe420]
2:
On Sun, Sep 30, 2007 at 02:12:29PM +0200, Steinar H. Gunderson wrote:
Since I upgraded X.org I can no longer press keys remotely. If I do so,
the X server crashes with:
It turns out that the input ABI changed with version 1.4.0 of the X server,
but since VNC does not register as an input driver
reassign 06 libwxgtk2.6-0
severity 06 grave
tags 06 pending sid
merge 06 441766
On Fri, Sep 28, 2007 at 12:23:24PM +0200, Jean-Michel Pouré wrote:
Description: VLC segfaults on startup when Gnome 2.6.20 is installed.
This is a bug in wxWidgets, not VLC; reassigning and merging.
On Sat, Sep 22, 2007 at 10:42:31AM -0700, David Liontooth wrote:
Package: nfs-kernel-server
Version: 1:1.1.0-13
Severity: normal
The command to unexport a directory appears to no longer have any effect.
I issue exportfs -u :/tv01 and exportfs shows /tv01 still exported;
consequently,
On Tue, Sep 18, 2007 at 04:53:56PM +0200, ingo wrote:
the switch to the new configuration format is mentioned in NEWS.Debian. I
don't know a better place to write such information. If you have a
suggestion, please let me know.
this file is not installed with libpam-mount 0.20-1
Indeed. By
severity 442017 grave
thanks
On Wed, Sep 12, 2007 at 05:16:39PM +0200, ingo wrote:
not sure where the real bug is in this but when upgrading to the current
version my setup, which was configured in the plain text configuration
files, stopped working because libpam-mount seemed to have silently
On Sat, Sep 15, 2007 at 04:37:33PM +0200, Per Hansen wrote:
So I tried to use squash_uids=0-2003,2005-.
But this fails with the following message:
Exporting directories for NFS kernel daemon...exportfs: /etc/exports:12:
unknown keyword 2005-
I looked at the code and found the
Package: dc
Version: 1.06.94-1
Severity: normal
Subject: dc: error reading input: Interrupted system call
Package: dc
Version: 1.06.94-1
Severity: normal
Hi,
Since forever, I've been exiting dc with Ctrl-C -- it might not be
correct, but it's always worked, and it's thoroughly fixed in my
severity 441361 wishlist
thanks
On Sun, Sep 09, 2007 at 12:11:41AM -0700, Steve Langasek wrote:
After rolling out IPv6 on my home network, I've taken a peek at whether I
could switch my NFS shares to IPv6 as well, which would let me simplify my
DNS resolution a bit.
But mount.nfs doesn't
On Sun, Sep 09, 2007 at 02:41:16AM +0200, Michael Biebl wrote:
could you please test the latest 0.6.5 packages and let me know if it
improved the situation for you?
No big difference on the non-encrypted WLAN here: Seems to work fine with
iwl3945, associates but gets no green dots nor an IP
On Fri, Aug 03, 2007 at 08:23:12AM +1000, Trent W. Buck wrote:
The two vnc packages should have the auto flag set, because they were
pulled in by xrdp's Recommends.
I believe I see a variant of this problem. I have several non-free packages
that should have been marked as removable by pkgsync
reassign 418596 initscripts
thanks
On Wed, Sep 05, 2007 at 02:22:48PM +1200, Phil Snowdon wrote:
Here's a first cut that does (2) with a slight modification to mountnfs.
This is a rather interesting approach, but it's outside the scope of what I
can approve/nix. I'm reassigning to initscripts,
On Mon, Sep 03, 2007 at 05:25:32PM +0200, Gebhardt Thomas wrote:
I consider this bug important enough to be fixed in stable etch.
Are you serious? It's an edge case that affects a tiny fraction of all users,
can by worked around in the majority of cases (simply mount NFS later in the
boot
reassign 440676 linux-image-2.6.18-5-powerpc
thanks
On Mon, Sep 03, 2007 at 11:38:31AM -0400, Jeffrey B. Green wrote:
The setup is having nfs mounts on various machines and backups to
non-local mounts. Having cron jobs starting on more than one machine and
backing up to the other while the
On Tue, Sep 04, 2007 at 09:25:19AM +1200, Phil Snowdon wrote:
However the issues still need to be addressed in Lenny/Sid.
The last thing I heard was that it was OK in sid... Did I misunderstand, or
are we talking about two different problems now?
/* Steinar */
--
Homepage:
On Fri, Aug 17, 2007 at 01:08:01AM +0200, Steinar H. Gunderson wrote:
I'll test with etch,lenny and sid and provide more information
Great, thanks.
Any progress on this?
/* Steinar */
--
Homepage: http://www.sesse.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
On Tue, Aug 14, 2007 at 04:08:17AM +0200, Steinar H. Gunderson wrote:
Hm, that's odd, it works just fine here (both default, and changing it).
Could you see if the issue is misparsing (ie., try to echo $RPCNFSDCOUNT in
/etc/init.d/nfs-kernel-server right before starting rpc.nfsd), or something
On Sat, Aug 25, 2007 at 04:06:21AM -0500, Nelson Castillo wrote:
The bug I reported is about the kernel message that is printed
all the times (it doesn't depend on portmap being bound to the loopback
address).
Oh. That's quite a different thing.
The message suggests something wrong I
On Mon, Aug 27, 2007 at 03:26:36PM -0500, Nelson Castillo wrote:
A quick Google search seems to indicate that others have the same problem,
but only when the kernel can't contact portmap. Yet, you're getting it even
if portmap is running... You're sure the loopback interface is up?
Yes. And no
On Mon, Aug 27, 2007 at 03:39:36PM -0500, Nelson Castillo wrote:
While you're at it, could you please also check that rpc.statd is running on
the server?
# ps ax|grep rpc
3116 ?Ss 0:00 /sbin/rpc.statd
3138 ?Ss 0:00 /usr/sbin/rpc.idmapd
3171 ?S 0:00
On Mon, Aug 27, 2007 at 04:04:38PM -0500, Nelson Castillo wrote:
nfsd: last server has exited
nfsd: unexporting all filesystems
RPC: failed to contact portmap (errno -5).
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
NFSD: starting 90-second grace period
Urrr.
On Mon, Aug 27, 2007 at 04:14:00PM -0500, Nelson Castillo wrote:
In my first post I noted that I got lockd_up: makesock failed, error=-5
once. In case I didn't make myself clear, It was only shown once.
You are not making yourself very clear, no. What _is_ the problem here,
really? Do you have
reassign 437525 linux-image-2.6.21-2-686
thanks
On Mon, Aug 27, 2007 at 04:32:42PM -0500, Nelson Castillo wrote:
As I told you before, I reported the bug (the message printed by
the kernel) because I found the message to be misleading and I
wasted some time with it.
OK, that wasn't really
On Thu, Aug 23, 2007 at 07:15:48PM +, Carlos Moffat wrote:
Do you happen to use the madwifi driver? A while ago I had the same
problem you're describing. The way I solved it was to do:
No, ipw3945.
There's movement in this case -- it now sort-of works, but not always, but I
don't have the
On Mon, Aug 20, 2007 at 04:45:20AM -0400, Justin Piszcz wrote:
Need to dig into this, it now happens on an x86 box, in particular, when
you run find /NFS_MOUNT/ across the root filesystem.
This sounds awfully lot like a duplicate of #435056. Could you try the latest
sid version and see if it
On Mon, Aug 20, 2007 at 12:15:50PM -0400, Justin Piszcz wrote:
Could you please remind me of the command? apt-get install -t unstable
nfs-kernel-server nfs-common?
Assuming you've got unstable in your sources.list, that should do fine. (You
don't really want to be using apt-get in 2007, though
On Mon, Aug 20, 2007 at 03:08:00PM -0400, Justin Piszcz wrote:
Very impressive! This solves the find problem, I will let you know if I
have any other issues.
Great to hear that it's probably the same problem. :-)
Is it safe to keep that version installed until the new-fixed version is
On Sat, Aug 18, 2007 at 07:00:54PM -0400, Justin Piszcz wrote:
Using these for now and without fsid=, will see if it happens again.
OK. Are you implying that this only happens every now and then? From your
initial description, it sounded like it was consistent. An strace of
rpc.mountd at the
On Fri, Aug 10, 2007 at 03:16:28PM +1200, Phil Snowdon wrote:
I wouldn't like to see this bug dropped as we still have issues with it.
My understanding is that mountnfs tries to mount the NFS shares as soon
as the first interface is available. We worked round this by changing
the order that
On Thu, Aug 16, 2007 at 03:58:15AM -0400, Justin Piszcz wrote:
Arch = x86_64
And does a downgrade help?
/* Steinar */
--
Homepage: http://www.sesse.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Thu, Aug 16, 2007 at 11:44:18AM -0400, Justin Piszcz wrote:
Unsure, I have mounted with the options I mentioned earlier and that seems
to have resolved the problems, all partitions are SW RAID 1 and 5 and the
mount daemon/etc does not appear to know how to deal with them after last
On Fri, Aug 17, 2007 at 10:52:18AM +1200, Phil Snowdon wrote:
I think the issue that is even though the mount is in the background, it
fails and the mount process exits.
Hm, well, it _is_ supposed to retry, but perhaps it doesn't for errors like
that?
I'll test with etch,lenny and sid and
On Wed, Aug 15, 2007 at 09:32:30PM -0500, Gunnar Wolf wrote:
Of course, before any action, I'd like to hear Thom's or Andres' points
of view.
You probably want to hear my input too. :-)
At Debconf5, I was more or less persuaded into taking the package (up to
the level where I actually had the
On Sun, Aug 12, 2007 at 11:33:38PM -0500, Nelson Castillo wrote:
I don't think it is clear at all. I'm talking about the default configuration
of nfs-kernel-server, that should at least work from localhost with no
extra configuration, IMHO.
If there is some reason that precludes
On Sun, Aug 12, 2007 at 04:37:01PM +0200, Steinar H. Gunderson wrote:
Uhm, are you saying that upgrading the server from 1:1.1.0-4 to 1:1.1.0-11
breaks rpc.mountd? That sounds very weird, as there's been exactly zero
changes to mountd in that timeframe...
Well I did not change anything
On Mon, Aug 13, 2007 at 03:47:06PM -0500, John Goerzen wrote:
RPCNFSDCOUNT in /etc/default/nfs-kernel-server -- and also
/etc/init.d/nfs-kernel-server -- seems to be ignored.
RPCNFSDCOUNT=8 is in our /etc/default/nfs-kernel-server.
But, according to both ps and /proc/fs/nfsd/threads,
only
On Sun, Aug 12, 2007 at 04:08:21AM -0400, Justin Piszcz wrote:
2007-07-28 04:18:43 status unpacked nfs-kernel-server 1:1.1.0-4
2007-07-28 04:18:43 status unpacked nfs-kernel-server 1:1.1.0-11
Uhm, are you saying that upgrading the server from 1:1.1.0-4 to 1:1.1.0-11
breaks rpc.mountd? That
On Sun, Aug 12, 2007 at 10:34:13AM -0400, Justin Piszcz wrote:
Uhm, are you saying that upgrading the server from 1:1.1.0-4 to 1:1.1.0-11
breaks rpc.mountd? That sounds very weird, as there's been exactly zero
changes to mountd in that timeframe...
Well I did not change anything on the client,
reopen 437342
thanks
On Sat, Aug 11, 2007 at 11:24:05PM +, Debian Bug Tracking System wrote:
Problem was I needed fsid=0 for the root filesystem and then it appears
that fixed the issue. (in /etc/exports)
Thank you for the report.
Closing it.
If fsid=0 is suddenly required that is a
On Sun, Aug 12, 2007 at 08:28:30PM -0500, Nelson Castillo wrote:
I'm using Debian sid and I upgraded the system today
(the last complete upgrade was about one month ago).
I get the failed to contact portmap errors.
Is the portmapper running at all? (ps aux | grep portmap)
I am stuck. I used
On Sun, Aug 12, 2007 at 09:35:48PM -0500, Nelson Castillo wrote:
BTW, the NFS troubleshooting documentation references a rcpinfo binary.
Is it obsoleted? Perhaps I need to install another package.
You probably mean rpcinfo. It's included in the libc6 package, so it's
definitely on your system.
Package: ftp.debian.org
Severity: normal
Hi,
mip6d has seen significantly less activity upstream than I expected at
the time I was uploading it, and it currently FTBFS due to ever-changing
kernel headers. There is a newer source _somewhere_, but it's rather
well hidden and probably requires a
On Sat, Aug 11, 2007 at 06:53:39PM -0400, Justin Piszcz wrote:
After apt-get upgrade, NFS no longer works:
Did you upgrade the server or the client? Which version did you upgrade from?
What does your /etc/exports look like?
/* Steinar */
--
Homepage: http://www.sesse.net/
--
To UNSUBSCRIBE,
On Sat, Jul 28, 2007 at 12:32:28PM +0200, Steinar H. Gunderson wrote:
I have just returned from vacation and have quite a few things to catch
up with here. But I will take a look at it. I do hope that nothing else
breaks (dependencies) as I am running stable here.
I can't guarantee that, sorry
Package: gcc-4.1
Version: 4.1.2-14
Severity: normal
Hi,
nfs-utils 1:1.1.1~git-20070706-2 FTBFS on alpha (and alpha only):
if gcc -DHAVE_CONFIG_H -I. -I. -I../../support/include
-I../../support/include -D_GNU_SOURCE -Wall -Wstrict-prototypes -mno-fp-regs
-ffixed-8 -pipe -g -O2 -Wall -MT
On Tue, Aug 07, 2007 at 10:34:12PM +0200, Steinar H. Gunderson wrote:
(insn 111 17 112 0 nfsstat.c:688 (set (mem/c:DF (plus:DI (reg/f:DI 30 kr
170 ($30))
Once more, without the Firefox currency converter enabled :-)
if gcc -DHAVE_CONFIG_H -I. -I. -I../../support/include
-I../../support
On Sun, Jan 01, 2006 at 06:45:47PM +0100, KnuX wrote:
When PC-Client is booting and PC-Server is unreachable (no network
connection, shut down machine, etc.), the boot process stop when it tries
to mount the PC-Server share.
Hi,
Since this, nfs-utils has taken over responsibility for
On Sun, Aug 05, 2007 at 08:53:08PM +0200, Steinar H. Gunderson wrote:
Hm. I'm trying to reproduce it now, and I can perhaps do it once out of ten.
Sort of hard to track down...
Finally!
I got it to be weird while I was stracing it. From there it was only a
matter of remembering the following
tags 432767 + lenny sid
thanks
On Sun, Aug 05, 2007 at 02:11:37PM +0200, Kurt Roeckx wrote:
If I understand this right, this bug doesn't affect etch since the
version of mount in etch is more forgiving?
Yes.
If that's the case, can you please tag this bug lenny sid?
Doing so now.
/*
On Sat, Jul 28, 2007 at 08:21:47PM -0400, Aron Griffis wrote:
server
--
mkdir -p /test/proc
mount -o bind /proc /test/proc
echo '/test 10.0.0.0/16(rw,no_root_squash,async,no_subtree_check)'
/etc/exports
exportfs -a
client
--
mkdir /test
mount server:/test /test
/bin/ls
On Sun, Aug 05, 2007 at 02:41:18PM -0400, Aron Griffis wrote:
If I put the server restart in a loop, the client makes slow progress.
Restarting just once does not alleviate the problem forever. It's
possible that I'm seeing it hang once per subdirectory, since I have
a number of mounts under
On Sat, Jul 28, 2007 at 09:33:38PM -0400, Aron Griffis wrote:
But NFS exports filesystems, so at least in theory, the /proc in there should
be ignored completely unless you export it.
Exactly. But instead it's hanging
Well, nfs-utils does not mess with the mount after it has handed it over to
On Sat, Jul 28, 2007 at 11:52:52AM +0200, Thomas Nilsson wrote:
I have just returned from vacation and have quite a few things to catch
up with here. But I will take a look at it. I do hope that nothing else
breaks (dependencies) as I am running stable here.
I can't guarantee that, sorry.
severity 435056 normal
thanks
On Sat, Jul 28, 2007 at 08:21:47PM -0400, Aron Griffis wrote:
When a client attempts to read a bind-mounted proc directory from the
server, the server never responds. Found this with wireshark and
narrowed down to a simple test. Other bind-mounts seem to be
On Sat, Jul 28, 2007 at 09:15:30PM -0400, Aron Griffis wrote:
I don't want to export my /proc, I want to export a filesystem that
has proc mounted on a subdir.
But NFS exports filesystems, so at least in theory, the /proc in there should
be ignored completely unless you export it.
On Mon, Jun 25, 2007 at 08:49:24PM +0200, Steinar H. Gunderson wrote:
Starting just after coming home from DebConf (I believe I updated my
machine the last day), I can suddenly no longer associate with any
networks -- open or not -- with network-manager. The progress indicator
just spins
On Sat, Mar 18, 2006 at 08:35:27AM -0500, Theodore Ts'o wrote:
Trying to get ext2prepare's functionality into e2fsprogs is still
pending... You _can_ do it using some careful use of debugfs and
e2fsck, but it's not very safe.
Any progress on this? Most of my filesystems are with the resize
reassign 434775 initscripts
thanks
On Thu, Jul 26, 2007 at 10:33:21AM -0700, Andy Sharp wrote:
When booted with ip= on the kernel command line, setting the IP
address, NFS volumns are not mounted because the logic of the
interlocking pieces believes that the interface(s) have not been brought
On Tue, Jul 24, 2007 at 11:24:08AM -0500, Dale Purdy wrote:
After upgrading from 1:1.1.0-4 version to 1:1.1.0-11 version, the
grpid option is no longer supported.
What is the option supposed to do?
/* Steinar */
--
Homepage: http://www.sesse.net/
--
To UNSUBSCRIBE, email to [EMAIL
On Mon, Jul 23, 2007 at 04:12:51PM +0200, Jochen Eisinger wrote:
mount.nfs shipped with nfs-common does not now about option (no)browse,
which is passed by automount (if present in auto.master). The result is
that it's not possible to access automounted nfs volumes.
Neither does the old mount:
On Tue, Jul 24, 2007 at 11:24:08AM -0500, Dale Purdy wrote:
After upgrading from 1:1.1.0-4 version to 1:1.1.0-11 version, the
grpid option is no longer supported.
Actually, I checked, and grpid is for ext2/ext3 file systems only. It does
not seem to be supported under NFS at all.
revert to
On Tue, Jul 24, 2007 at 01:42:18PM -0500, Dale Purdy wrote:
Perhaps the 1:1.1.0-4 version was filtering out the grpid option so
that the mount still took place.
I've considered the same, but it really doesn't make sense. Could you please
try a manual mount with 1:1.1.0-4 and 1:1.1.0-11? I'm
On Fri, Jul 20, 2007 at 07:26:09AM -0700, David Liontooth wrote:
Please close -- but this should be documented (or the default changed to
what used to be in effect before nfs-common 1.1.0-6).
Thanks, closing.
BTW, it seems upstream thinks it is not a bug that there's no fallback to
UDP, as it
retitle 434387 mount should pass -s to mount.* helpers
reassign 434387 mount
forcemerge 434387 434528
thanks
On Tue, Jul 24, 2007 at 09:46:12PM +0200, Jochen Eisinger wrote:
the point is, mount from util-linux does not pass the -s (sloppy) option
to external mount commands. That's why mount.nfs
On Tue, Apr 10, 2007 at 08:43:41PM +0200, Thomas Nilsson wrote:
I have two network interfaces on worktoo. One comes up as eth0 during boot.
This is a 10/100 interface.
The second is eth2 which is a 1000 Mb/s connected to a NAS.
Hi,
It seems like I've gotten this bug back into my lap due to
On Sat, Jul 21, 2007 at 03:36:11PM +0200, Folkert van Heusden wrote:
When I want to install nfs-kernel-server, it wants to remove all kinds
of non-related packages:
Could you please include the entire command line and the _entire_ output from
apt?
/* Steinar */
--
Homepage:
On Thu, Jul 19, 2007 at 07:53:25PM -0700, David Liontooth wrote:
In /etc/fstab, I use this line to mount an NFS drive behind a firewall that
forwards ports with iptables:
system:/esb /mnt/esb1 nfs
noauto,user,exec,rw,rsize=16k,wsize=16k,hard,intr,port=4000,mountport=5000 0 0
Could you try
On Wed, Jul 18, 2007 at 05:28:42PM -0600, Bruce Sass wrote:
This doesn't work for me, it kinda makes things worse because now the
messages telling me that statd isn't running disappear off the screen
before I can read them.
OK, thanks.
I can manually start rpc.statd, then mount the missing
On Thu, Jul 19, 2007 at 03:58:58AM -0600, Bruce Sass wrote:
First thing I tried (with the -10 build, both by adding it to the
options list in fstab and mount -o...), mount complained that nolocks
was unsupported by(for?) nfs.
Hm, that's interesting. I'll check it out at some point.
I'll
Version: 1:1.1.0-10
On Tue, Jan 30, 2007 at 10:14:51PM -0500, Robert Edmonds wrote:
The attached patch removes them.
This seems to have been already fixed in the new mount.nfs, so I'm marking it
as closed.
/* Steinar */
--
Homepage: http://www.sesse.net/
--
To UNSUBSCRIBE, email to [EMAIL
On Tue, Jul 17, 2007 at 04:22:24PM +0200, Ivan Sergio Borgonovo wrote:
I had to downgrade nfs-common to make it work.
nfs-common_1%3a1.1.0-10_amd64.deb
still doesn't work.
Try setting ASYNCMOUNTNFS=no in /etc/default/rcS. I'm currently talking to
the initscripts maintainers to try to find a
reassign 433386 initscripts
tags 433386 + patch
thanks
Hi,
As discussed with Petter on IRC, initscripts is going to need fixing in
addition to the latest nfs-common changes. The following patch is a fixed
version of a previous patch I proposed; I've been asked to wait for feedback
for a few days
On Sun, Jul 15, 2007 at 03:20:57PM +0200, Elimar Riesebieter wrote:
Starting NFS common utilities: statd.
mount.nfs: rpc.statd is not running but is required for remote locking
Either use -o nolocks to keep locks local, or start statd.
So statd doesn't want to start. Perhaps it would like
Package: initscripts
Version: 2.86.ds1-38
Severity: normal
Hi,
As discussed on IRC, you'll need to make the mountnfs init script depend
(via LSB headers) on nfs-common. Also remember to remove the hack for
calling nfs-common and portmap directly, now that nfs-common is at S44. :-)
-- System
On Mon, Jul 16, 2007 at 10:14:17PM +0200, Elimar Riesebieter wrote:
What the heck are you fixing, he?
Did it backfire? That's not good. If you do ls -l /etc/rcS.d/S4*, what does
it output? (The interesting parts would be S43portmap, S44nfs-common and
S45mountnfs.sh -- are all of them there?)
/*
On Mon, Jul 16, 2007 at 11:10:26PM +0200, Elimar Riesebieter wrote:
lrwxrwxrwx 1 root root 20 Jul 14 2006 /etc/rcS.d/S40networking -
../init.d/networking
lrwxrwxrwx 1 root root 17 Jul 14 2006 /etc/rcS.d/S43portmap -
../init.d/portmap
lrwxrwxrwx 1 root root 20 Jul 16 22:03
On Mon, Jul 16, 2007 at 11:49:51PM +0200, Elimar Riesebieter wrote:
Please find attached bootlog.-
Thanks, but this doesn't make any sense! :-)
Mon Jul 16 23:44:01 2007: Setting up networking
Mon Jul 16 23:44:01 2007: Configuring network interfaces...Internet Systems
Consortium DHCP
On Sun, Jul 15, 2007 at 02:28:35AM -0400, Simon Ruggier wrote:
I happen to have written source packages for various versions of
stepmania with cdbs-style rules files, hosted at
http://www.eng.uwaterloo.ca/~sruggier/files/apt/. There are three
versions - one of the 4.0 versions is from a
On Sun, Jul 15, 2007 at 01:28:32PM +0200, Elimar Riesebieter wrote:
Doesn't work in addition to nfs-common 1.1.0-9.
What does your fstab look like? What messages do you get during boot?
(I'm taking this off debian-devel from here on; it doesn't make sense to keep
debugging there.)
/* Steinar
On Sun, Jul 15, 2007 at 02:06:21PM +0200, Elimar Riesebieter wrote:
rpc.statd is not running but is required for remote locking
Either use -o nolocks to keep locks local, or start statd.
--- mountnfs.orig 2007-07-13 12:01:18.0 +0200
+++ mountnfs2007-07-15 13:38:21.0
On Thu, Jun 14, 2007 at 05:18:38PM +0200, Bart Cortooms wrote:
We're using drbd+heartbeat+nfs as well, and the symptoms are the same: when
calling /etc/init.d/nfs-kernel-server stop from the command line all
threads are stopped cleanly. When heartbeat calls
/etc/init.d/nfs-kernel-server
reassign 432767 cfs
severity 432767 grave
thanks
On Wed, Jul 11, 2007 at 10:39:12PM +0200, Martin Waitz wrote:
after upgrading to nfs-common 1.1.0-6 cfs 1.4.1-17 does not work any more.
I get the following messages when running cfsd manually on the console:
mount: mount to NFS server
reassign 433119 initscripts
forcemerge 432750 433119
thanks
On Sat, Jul 14, 2007 at 04:53:54PM +0200, Frans Pop wrote:
Since the upgrade from 1:1.1.0-6, my system no longer mounts an NFS
volume listed in my /etc/fstab during system boot (I did no other
relevant upgrades that day). It mounts
On Sat, Jul 14, 2007 at 06:17:13PM +0200, Frans Pop wrote:
I'm not all that interested in what the right long-term fix is, I'm
concerned about a change in nfs-common breaking something semi essential
that has worked for ages, accidentally or not.
I'm a bit unsure why this suddenly started
tags 433119 + patch
thanks
On Sat, Jul 14, 2007 at 07:40:13PM +0200, Frans Pop wrote:
I'm a bit unsure why this suddenly started going to debian-devel; I'm
Cc-ing the bug again, at least.
Because I CCed it there, but you only replied to d-devel :-)
OK, my bad.
Try this patch:
The patch
On Sat, Jul 14, 2007 at 10:22:52PM +0200, Miriam Ruiz wrote:
I plan to upload version 3.9 to the archive. AFAIK, there shouldn't been
ant problem with the theme, as it is original and, even if it tries to
mimig DDR's, no TM is being enforced.
We discussed this on IRC, so I'll just put the
reassign 248300 linux-source-2.6.18
thanks
On Sat, Jul 14, 2007 at 11:04:07PM +0200, Lars Ellenberg wrote:
Could a reassign be appropriate?
yes. IMO, it is likely some race condition in kernel nfs code.
Then reassigning to 2.6.18. Thanks for the analysis.
/* Steinar */
--
Homepage:
fixed 346146 1:1.1.0-4
thanks
On Thu, Jul 05, 2007 at 02:02:41PM +0200, Wolfgang Walter wrote:
rpc.statd -p 900 -o 901
does not work in etch (it does in sarge).
The reason is that rpc.statd changes its uid to user statd and therefore is
not allowed to open ports 1024.
It does work just
On Fri, Jul 13, 2007 at 06:43:35PM +0200, giggz wrote:
fews days ago I opened a bug (#432581). The new version allows now to mount
the NFS exports with Drivemount from gnome-applets without problem (thx for
that!). but when I unmount the volume, I get an error. But I can't tell
which one,
reassign 432750 initscripts
forcemerge 432511 432750
thanks
On Wed, Jul 11, 2007 at 08:45:02PM +0200, Elimar Riesebieter wrote:
Hey, util-linux 2.13~rc1 resides in experimental! Unstable version of
nfs-common isn't able to mount nfs-shares at boottime:
That's something that needs to be fixed
On Wed, Jul 11, 2007 at 10:39:12PM +0200, Martin Waitz wrote:
after upgrading to nfs-common 1.1.0-6 cfs 1.4.1-17 does not work any more.
I have no idea what CFS is, I'm afraid :-)
I get the following messages when running cfsd manually on the console:
mount: mount to NFS server 'localhost'
On Wed, Jul 11, 2007 at 10:42:08PM +0200, Elimar Riesebieter wrote:
Hey, util-linux 2.13~rc1 resides in experimental! Unstable version of
nfs-common isn't able to mount nfs-shares at boottime:
That's something that needs to be fixed in initscripts.
Why?
Because initscripts is what's dealing
On Wed, Jul 11, 2007 at 03:21:52AM +0200, Frank Lichtenheld wrote:
this package doesn't build anymore because it depends on a now non-existant
package.
Thanks for the bug report. Unfortunately, upstream's sources (neither from
git nor svn) build with 2.6.21. I'll wait a couple of months -- if
reassign 432511 initscripts
thanks
On Tue, Jul 10, 2007 at 11:26:51AM +0200, Rasmus Bøg Hansen wrote:
statd should be started at boot before trying to mount NFS volumes from
fstab as 2.6.22 seems to want statd running before mount:
nfs-common doesn't really do this kind of thing, initscripts
701 - 800 of 1960 matches
Mail list logo
