RE: [leaf-user] Dachstein-CD 1.0.2 + Qmail 1.03a Runaway conditio n

[Wrigglesworth, C. <Col...@ra...>]

Charles,
	You hit the problem right on the head, then I guess you would.

I ended up modifying the qmail init script to create the 'missing'
directories because it was simple and the qmail298 script takes care of any
permissions problems I might have got wrong.

I didn't quite follow how to do it the 'tidy' way but that is just in
experience on my part. Also even stopping the logging daemon I couldn't
unmount /var/log getting the message 'device or resource busy'.

Now to start testing it proper and find out what else I don't understand.
;-/

Thanks

Colin
	-----Original Message-----
	From:	Charles Steinkuehler [SMTP:ch...@st...]

	I have not added qmail to Dachstein, but I think I know what's going

	wrong.  Dachstein uses a seperate partition for the log files, so 
	/var/log is empty at boot (when the *.lrp files are automatically 
	unpacked/installed).  Init scripts mount the /var/log partition, and

	populate it with the required files/directories.  The qmail package 
	probably contains /var/log/smtp and /var/log/pop3 files, but they
are 
	getting over-written when the new /var/log partition is mounted.

	What I think is happening at boot-time:

	- Dachstein boots, loads the kernel, initial ramdisk (root.lrp) and
runs 
	the /linuxrc init script

	- linuxrc installs all packages, including qmail.lrp

	- The installation of qmail.lrp creates the desired
files/directories in 
	/var/log

	- linuxrc exits, and init takes over.

	- rcS.d scripts are run, creating a new ramdisk and mounting it at 
	/var/log.  This causes the existing /var/log/ files to "dissappear"

	- qmail init script runs, and qmail barfs on non-existant files.

	There are a couple of ways you can fix this.  First, you can test
for 
	(and create if missing) the files you expect in the qmail init
script. 
	Make sure you get the ownership and permissions correct, or qmail
will 
	continue to complain.

	The clean way to do this, however, is to put a tar.gz file in 
	/etc/ramdisk/.  The files in this directory are uncompressed *AFTER*
all 
	additional run-time ramdisks are created and mounted, allowing you
to 
	populate /var/log (and any other directories that might be on their
own 
	ramdisk partiton) after system init.  Simply create a tar.gz file
with 
	the required /var/log entries (use the existing log.tgz as an
example), 
	drop it in /etc/ramdisk/, and add it to the qmail file list so it
will 
	be backed up with the qmail.lrp package.  For extra-credit, you can 
	remove the /var/log entries from the qmail.lrp package so they won't
be 
	hanging around chewing up memory (NOTE:  The /var/log files
installed 
	from the qmail.lrp package didn't entirely disappear, you just can't
see 
	them until you unmount /var/log.  To test this, shutdown the logging

	daemons with svi sysklogd stop, and unmount /var/log...the missing
qmail 
	files should magically appear!).

	-- 
	Charles Steinkuehler
	ch...@st...
	


*******************************************************************************************************
The information contained in this e-mail is confidential. It may also be legally privileged. It is intended only for the stated addressee(s) and access to it by any other person is unauthorised. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. Such unauthorised use may be unlawful.

If you have received this e-mail in error, please inform RACAL INSTRUMENTS LTD. immediately by phoning +44 (0)1628 604455 (ask for the I.T. dept) and delete it and all copies from your system.
*******************************************************************************************************