Path: utzoo!attcan!uunet!munnari!otc!metro!ipso!runx!brucee
From: brucee@runx.ips.oz (Bruce Evans)
Newsgroups: comp.os.minix
Subject: Re: /etc/umount & /etc/update
Message-ID: <1896@runx.ips.oz>
Date: 20 Dec 88 19:30:50 GMT
References: <5982@louie.udel.EDU>
Reply-To: brucee@runx.OZ (Bruce Evans)
Organization: RUNX  Un*x Timeshare. Sydney, Australia.
Lines: 30

Chip Roberson writes:
>	I then restarted update (/etc/update &)
>		while cd'd into a /usr subdir
>	I then cd'd to / and tried to
>		/etc/umount /dev/at0	(where /usr was mounted)
>	which told me that it was busy.
>
>I had no other processes running.  I then killed /etc/update
>and I could umount /dev/at0.
>
>Can someone please explain to me why umount thought /dev/at0 was busy.

Updates's current directory was still active.

I fixed this by putting

	chdir("/");

in update.c. Cron.c has the same problem. I had previously wondered why
cron was locking my /usr partition. But it must be something else, cron
started from /etc/rc (it is an old unofficial version anyway).

When I tried the fix for cron.c (both versions), I had to fix some other
problems. Cron.c closes stdio rather than fclosing it. This confused my
version of stdio (probably my fault). Then cron couldn't handle leading
white space. My usual crontab is empty, so I copied one of the examples,
but this exposed the bug.

Bruce Evans
Internet: brucee@runx.ips.oz.au    UUCP: uunet!runx.ips.oz.au!brucee