On Thu, Jun 05, 2003 at 01:03:17AM +0200, Bernd Walter wrote:
> On Wed, Jun 04, 2003 at 02:21:29PM -0700, jle wrote:
> > on HTTPD: (/etc/fstab)
> > NFSD:/home2 /home nfs rw,bg 0 0
> ed /etc/fstab
> /home2
> s/home/home2/
> w
> q
Don't exactly do this sin
> > [EMAIL PROTECTED]:~ -13:55:06- # cd ~dkdesign
> > -su: cd: /home2/dkdesign: No such file or directory
>
> Not surprising, because you mounted on /home not /home2.
There shouldn't BE a /home2 on HTTPD but I figured out what happened. I
copied /etc/group /etc/passwd /etc/pwd.db and /etc/master.p
On Wed, Jun 04, 2003 at 02:21:29PM -0700, jle wrote:
> I retired my old p200 fbsd 4.4-stable web server and built a newer box for
> it. I used to mount the /home2 dir from my nfs server (fbsd 5.1-current)
> to /home on the webserver and it used to work fine but now it doesn't
> mount /home2 on /ho
Alfred Perlstein writes:
>This is freebsd following the NFS spec, please read the mount_nfs
>man page for the workaround (hint: intr).
In my experience the 'intr' filesystem mount option does not always
work. As an example, I am often unable to abort from a hung 'df' when a
remote NFS server is
On Wed, 31 Mar 1999, Thomas Schuerger wrote:
> Hi!
>
> I'm experiencing serious NFS problems, when
> a remote NFS directory (also on FreeBSD) mounted on my
> machine goes down for whatever reason (e.g. normal
> shutdown). From then on, any processes accessing the mounted
> NFS directory (e.g. exe
>> This reminds me; do we have a utility to reference wmesg strings back
>> to the code that sets them, a la TAGS? Would this be useful?
> No, and yes respectively.
Okay, I've got an early version written. It's got some fairly
substantial TODO's, and needs a fair bit of cleanup. I would
appreci
On 23 Feb 1999, Joel Ray Holveck wrote:
> >> This reminds me; do we have a utility to reference wmesg strings back
> >> to the code that sets them, a la TAGS? Would this be useful?
> > No, and yes respectively.
>
> I have the scanner mostly written; there is one bug yet to fix (This
> time for s
>> This reminds me; do we have a utility to reference wmesg strings back
>> to the code that sets them, a la TAGS? Would this be useful?
> No, and yes respectively.
I have the scanner mostly written; there is one bug yet to fix (This
time for sure!). Presently, it creates a single file WTAGS whi
On 22 Feb 1999, Joel Ray Holveck wrote:
> >> The program on the client side always freezes (top reports it's
> >> STAT as 'D').
> > You need to pass the 'l' switch to ps and look at the 'wchan' column to
> > see where it's actually stuck.
>
> This reminds me; do we have a utility to reference w
> >> The program on the client side always freezes (top reports it's
> >> STAT as 'D').
> > You need to pass the 'l' switch to ps and look at the 'wchan' column to
> > see where it's actually stuck.
>
> This reminds me; do we have a utility to reference wmesg strings back
> to the code that sets
>> The program on the client side always freezes (top reports it's
>> STAT as 'D').
> You need to pass the 'l' switch to ps and look at the 'wchan' column to
> see where it's actually stuck.
This reminds me; do we have a utility to reference wmesg strings back
to the code that sets them, a la TA
> I update 3-Stable nearly weekly, and have been experiencing the same problem
> for quite a while now. NFS imports, on the client side appear to be losing
> data. When this occurs, I see .nfs78969 files on the server side.
These files exist because they've been deleted but not closed; this is
12 matches
Mail list logo
