Hi -
Thanks to all from the "second batch" that responded to my query. The
solutions are all valid. For our case I will symlink the spool area to
an emptier filesystem...
Best
George
"Balfour, Scott (Eurosoft)" <scott.balfour-eds@eds.com>
"Gowda, Sanjay" <sanjay.gowda@wilcom.com>
gabriel rosenkoetter <gr@cs.swarthmore.edu>
kevin@joltin.com (Kevin Sheehan {Consulting Poster Child})
Edwards Philip M Ctr AFRL/SNRR <Philip.Edwards@sn.wpafb.af.mil>
Matt Reynolds <matt@aztek-eng.com>
Anderson de Oliveira <anderson@tecgraf.puc-rio.br>
I usually put /var on its own partition.This saves me some headaches that
root filling up causes.You might want
to point that users spool to /tmp.
"Gowda, Sanjay" <sanjay.gowda@wilcom.com>
IF you have any any other filesystems or disks mounted
on your system, have you thought about linking /var/spool
directory to a directory on another partition other than /
Hope that helps.
- Sanjay
PS: Just a suggestion. A good practice is to keep the
/var and /tmp partition separate because these are the
directories to which users and programs write to and hence
tend to fill up. Like I said, it is just a suggestion and
since I have been burnt with the above problem that is what
I have been doing ever since :-)
gabriel rosenkoetter <gr@cs.swarthmore.edu>
Keeping /var on the same partition as / is a generally bad idea on a
system with a lot of users.
Logs go there too, lots of stuff that can fill up in a hurry.
You *could* implement quotas for /var/spool/print, I suppose... but
having it on a partition away from the vital stuff on / is probably a
better idea.
kevin@joltin.com (Kevin Sheehan {Consulting Poster Child})
Quotas??
Edwards Philip M Ctr AFRL/SNRR <Philip.Edwards@sn.wpafb.af.mil>
What is the user using to perform the printing? Recent versions of Solaris
(using the lp subsystem) by default create symlinks to the target files,
instead of copying them, for precisely this reason.
Other printing commands take an argument to specify symlinks; I believe lpr
takes a -s option.
Matt Reynolds <matt@aztek-eng.com>
Yes -
Find a mounted disk with alot of space (more than sufficient for this job
and others), then do the following (as root):
1. /etc/init.d/lp stop (stop the lp spooler and scheduler)
2. cd /var
3. tar cvf /tmp/l ./spool (create a tar file of the spool directory)
4. cd /<big file system> (change to the big file system directory)
5. tar xvf /tmp/l (untar the spool directory)
6. cd /var
7. rm -r spool (remove the old spool directory)
8. ln -s /<big file system>/spool (link the new directory into /var)
9. /etc/init.d/lp start (restart spooler)
This should do it.
Anderson de Oliveira <anderson@tecgraf.puc-rio.br>
You can create a link to another spool area but, if the user is using
lpr, he can try "lpr -s -P<printer> <file>". This command doesn't
copy the huge file into the spool area, but just makes a symbolic
link. It works.
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:25 CDT