On Thu, 6 Jun 1996, Fundamental wrote: > The only thing that could be the problem (?) is that i have a softlink > from my mailbox in /var/spool to my home directory (because my / is > full)
You probably should have partitioned the disk so that /var and/or /var/spool were separate partitions. Too late for that now, unless you want to reformat. You can still add another drive and mount a partition as /var if you want. Another way to do this is to move the mail spool directory to a partition with more space available. e.g. if /usr has lots of free space, try doing the following: mkdir -p /usr/spool cp -af /var/spool/mail /usr/spool rm -rf /var/spool/mail ln -s /var/spool/mail /usr/spool/mail This is the reason why i tend to mount extra drives/partitions as general purpose directories (e.g. /usr1, /usr2, /usr3 etc) rather than as special purpose directories (e.g. /var/spool/mail, /var/spool/news). It gives me the flexibility to move spool directories etc around on my system from one disk to another, and just change the sym link in /var/spool to point to the new location. e.g. on my system, /usr2 (a 540MB quantum scsi) has a directory called /usr2/spool. /usr3 (a 650MB Micropolis scsi) also has /usr3/spool. news spool is in /usr2/spool/news, and mail is in /usr3/spool/mail. I want nn's database on a separate drive from the main news spool (to minimise disk thrashing) so that's in /usr3/spool/nn. With appropriate sym links in /var/spool, I don't even have to recompile anything - it all works transparently to the programs. $ ls -alF /var/spool | grep -- "->" lrwxrwxrwx 1 root root 16 Jun 10 17:32 mail -> /usr3/spool/mail/ lrwxrwxrwx 1 root root 16 Jun 10 17:32 news -> /usr2/spool/news/ lrwxrwxrwx 1 root root 14 Jun 10 17:32 nn -> /usr3/spool/nn/ Some people will probably think that this is an ugly way of doing things - and i can see their point. But for me, the flexibility is worth a little bit of ugliness. Craig