Sun Solaris stops compiling
Hi All, I hope this email gets through Its. my 14th one and having no luck sending email to the group. I'm trying to compile the amanda-2.4.4.p1 client on Solaris 9 and it stops at config.status: executing depfiles commands. Any ideas what I need to do??? Todd Zenker CNE-Raytheon ITSS NASA-Goddard Space Flight Center Mailstop 200.1 BLDG 12 E036 Greenbelt, MD 20771
Re: Sun Solaris stops compiling
On Thursday 19 August 2004 06:11, todd zenker wrote: Hi All, I hope this email gets through Its. my 14th one and having no luck sending email to the group. First one we've seen Todd. Firewall problem on your end maybe? I'm trying to compile the amanda-2.4.4.p1 client on Solaris 9 and it stops at config.status: executing depfiles commands. Any ideas what I need to do??? Are you doing the configure and make as the user 'amanda'? Who should be a member of the group 'disk'? This is the usual on a linux box, but we've got a sol user here who can probably be a lot more specific in this regard. Jon? Jump right in.. Todd Zenker CNE-Raytheon ITSS NASA-Goddard Space Flight Center Mailstop 200.1 BLDG 12 E036 Greenbelt, MD 20771 -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.24% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
Re: Sun Solaris stops compiling
todd zenker wrote: I'm trying to compile the amanda-2.4.4.p1 client on Solaris 9 and it stops at config.status: executing depfiles commands. Define stop. Any message? Does it simply hang? For how long did you wait? Do you get a shell prompt back? After how long? Is the program waiting for some unresponsive network filesystems? If you're compiling anyway, why did you choose an old version? Current stable is 2.4.4p3. Does configure of other programs (e.g. gnutar) behave the same? Any ideas what I need to do??? More coffee? -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
samba does not support exclude list
Hi
I have enabled the exclude list on the amanda.conf file and i am backing
up windows folders through samba.
My Dumptype is
define dumptype root-tar {
global
program GNUTAR
comment root partitions dumped with tar
compress none
index
exclude list /usr/local/etc/amanda/exclude/exclude
priority low
}
Can any one help me in fixing the below error
[EMAIL PROTECTED] amanda]$ amcheck DailySet1
Amanda Tape Server Host Check
-
Holding disk /amhold: 8498704 KB disk space available, that's plenty
NOTE: skipping tape-writable test
Tape DailySet104 label ok
NOTE: info dir
/var/lib/amanda/DailySet1/curinfo/indus.mumbai.redhat.com/_home_ghetto_:
does not exist
NOTE: index dir
/var/lib/amanda/DailySet1/index/indus.mumbai.redhat.com/_home_ghetto_:
does not exist
Server check took 3.681 seconds
Amanda Backup Client Hosts Check
ERROR: indus.mumbai.redhat.com: [samba does not support exclude list]
ERROR: indus.mumbai.redhat.com: [samba does not support exclude list]
Client check: 2 hosts checked in 10.164 seconds, 2 problems found
(brought to you by Amanda 2.4.4p1)
[EMAIL PROTECTED] amanda]$
Would appreciate if anyone can help me
--
Regards,
Kaushal Shriyan
Technical Engineer
Red Hat India Pvt. Ltd.
Tel : +91-22-22881326/27
Fax : +91-22-22881318
Cell : +91-9820367783
Re: samba does not support exclude list
Hi,
amanda told you the problem:
samba does not support a exclude list in conjunction with amanda.
for backups using samba you can only define a single file to exclude.
The used client does not support more than one file to exclude, nor does
it support exclude-lists.
Christoph
Kaushal Shriyan schrieb:
Hi
I have enabled the exclude list on the amanda.conf file and i am backing
up windows folders through samba.
My Dumptype is
define dumptype root-tar {
global
program GNUTAR
comment root partitions dumped with tar
compress none
index
exclude list /usr/local/etc/amanda/exclude/exclude
priority low
}
Can any one help me in fixing the below error
[EMAIL PROTECTED] amanda]$ amcheck DailySet1
Amanda Tape Server Host Check
-
Holding disk /amhold: 8498704 KB disk space available, that's plenty
NOTE: skipping tape-writable test
Tape DailySet104 label ok
NOTE: info dir
/var/lib/amanda/DailySet1/curinfo/indus.mumbai.redhat.com/_home_ghetto_:
does not exist
NOTE: index dir
/var/lib/amanda/DailySet1/index/indus.mumbai.redhat.com/_home_ghetto_:
does not exist
Server check took 3.681 seconds
Amanda Backup Client Hosts Check
ERROR: indus.mumbai.redhat.com: [samba does not support exclude list]
ERROR: indus.mumbai.redhat.com: [samba does not support exclude list]
Client check: 2 hosts checked in 10.164 seconds, 2 problems found
(brought to you by Amanda 2.4.4p1)
[EMAIL PROTECTED] amanda]$
Would appreciate if anyone can help me
Re: samba does not support exclude list
Kaushal Shriyan wrote: Can any one help me in fixing the below error ... ERROR: indus.mumbai.redhat.com: [samba does not support exclude list] Means you cannot use exclude list with samba. (you may exclude one file, not a list of files). -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: Question: backup just 1 file
Sebastian Kösters wrote:
at the moment Amanda backups different dirs from different servers.
An entry in disklist looks like this:
server /dir hard-disk-tar
Now the question.
Is it possible to backup just a single file (like /etc/passwd for example)?
With a recent Amanda version (at least 2.4.3), and using GNUTAR,
you can have a disklist entry like:
server /etc/passwd /etc {
hard-disk-tar
include ./passwd
}
Note the disklist entry is indeed 4 lines.
The first /etc/passwd is just an arbitary string that must be unique
in the disklist for that host (if you omit it, it is assumed equal to
the disk/topleveldirectory).
The second /etc is the top level directory.
You can have an inline dumptype by put a brace+newline where the
normal dumptype should be.
There we include the normal hard-disk-tar that you already have,
and add the include directive to limit only to that one file or
directory.
If yes what entry has to be made in disklist and what's about the curinfo
and index dirs in /var/lib/amanda?
curinfo and indexes are fine.
--
Paul Bijnens, XplanationTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...*
* ... Are you sure? ... YES ... Phew ... I'm out *
***
Monthly to DVD
I want to write a full dump to a DVD, once a month. We're happy with intermediate tapes but would like to take a monthly snapshot of the archive. It will fit on a DVD so we're not talking enormous backups here. What configuration does Amanda need to extract a compress full monthly dump? Can this be done through amrestore? Is there any way to dump a compressed amanda archive to a file? And doesn't amanda spread full dumps througout the dump cycle anyway, making it hard to get a complete dump of lots of entries in disklist at the same time? Gaby -- Ha! Ha! Ha! Dislocation... - Phil Ken Sebben [EMAIL PROTECTED] http://vanhegan.net
Re: Monthly to DVD
Gaby Vanhegan wrote: I want to write a full dump to a DVD, once a month. We're happy with Fine. No problem. I do that once a week, but use tapes (220 Gbyte). The tapes are stored offsite. intermediate tapes but would like to take a monthly snapshot of the archive. It will fit on a DVD so we're not talking enormous backups here. What configuration does Amanda need to extract a compress full monthly dump? I don't understand this question, I believe. What is a compress full monthly dump? If you mean a gzip-compressed tar (or dump) archive, then you only need gunzip and tar (or restore) to extract the data. Having amanda utilities available, like amrestore, helps, but it not a requirement (use dd bs=32k skip=1 to jump over the amanda header to the compress full monthtly dump, as explained in docs/RESTORE). Can this be done through amrestore? Is there any way to dump a compressed amanda archive to a file? ??? It is a file already? Or do you mean the compressed tar/dump image just after the 32k byte header amanda adds? (That header even contains the commands you need to extract the backups!) And doesn't amanda spread full dumps througout the dump cycle anyway, making it hard to get a complete dump of lots of entries in disklist at the same time? Spreading over a dumpcycle of 0 days is what you want. Make a separate config named e.g. Archive and set dumpcycle 0. Run that config on the needed day instead of the daily. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: Sun Solaris stops compiling
When I run ./configure --with-user=amanda --with-group=disk, I dont get an error, I get a command prompt right after the config.status: executing depfiles commands. It looks like I can start to run make, but there is no make to run. I know this is a simple thing becuase a ran into the same problem a long long time ago and don't remember what I did... I'm getting to old to remember what I did last week. My shell is BASH. I put almost every path I can thin of the script would use. Not sure what else. Any more ideas??? Let me know Thanks Todd On Thu, 19 Aug 2004 12:37:16 +0200, Paul Bijnens [EMAIL PROTECTED] wrote: todd zenker wrote: I'm trying to compile the amanda-2.4.4.p1 client on Solaris 9 and it stops at config.status: executing depfiles commands. Define stop. Any message? Does it simply hang? For how long did you wait? Do you get a shell prompt back? After how long? Is the program waiting for some unresponsive network filesystems? If you're compiling anyway, why did you choose an old version? Current stable is 2.4.4p3. I have had problems with this old version until now. hahahehe... Does configure of other programs (e.g. gnutar) behave the same? Any ideas what I need to do??? More coffee? -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] -- Todd E. Zenker
Re: Sun Solaris stops compiling
Todd Zenker wrote: When I run ./configure --with-user=amanda --with-group=disk, I dont get an error, I get a command prompt right after the config.status: executing depfiles commands. I get this output (it could be different when ran the very first time, of after make distclean): ... lots of lines... config.status: creating tape-src/Makefile config.status: creating config/Makefile config.status: creating Makefile config.status: creating config/config.h config.status: config/config.h is unchanged config.status: executing depfiles commands config.status: executing common-src/amanda-int.h commands config.status: creating common-src/amanda-int.h : _AMANDA_COMMON_SRC_AMANDA_INT_H config.status: common-src/amanda-int.h is unchanged It looks like I can start to run make, but there is no make to run. no make to run??? You mean there is no Makefile? It should be been created just before. Is it there? Does it contain normal stuff? Maybe you have some old invalid config from another architecture in the tree? Did you run make distclean in that case? (I don't know how to do that if there isn't a Makefile, which should have been created...) Out of diskspace? Permission problems (e.g. root on an nfs-mount)? I know this is a simple thing becuase a ran into the same problem a long long time ago and don't remember what I did... I'm getting to old to remember what I did last week. My shell is BASH. I put almost every path I can thin of the script would use. Not sure what else. Too long paths make things confusing, or maybe you run into silly limits on environment length in Solaris? (Don't know the maximumum, one some Unix-variant, long time ago, it was 10Kbytes; I believe Solaris 9 has much higher limits). Also having directories in paths that point to retired nfs mounted or automounted directories can result in weird behaviour. Any more ideas??? Let me know I guess you did try to tar -zxvf amanda.xxx.tar.gz in a clean directory and try fresh again? Did you try more caffeine? Did you try more sleep? (first the latter then the former, not reversed) -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: Sun Solaris stops compiling
On Thu, Aug 19, 2004 at 09:47:42AM -0400, Todd Zenker wrote: When I run ./configure --with-user=amanda --with-group=disk, I dont get an error, I get a command prompt right after the config.status: executing depfiles commands. It looks like I can start to run make, but there is no make to run. I know this is a simple thing becuase a ran into the same problem a long long time ago and don't remember what I did... I'm getting to old to remember what I did last week. There are several of us around like that :) You say there is no make to run. Do you really mean make or no makefile (or Makefile)? One is a program that must be installed as a system developer utility, the other is the control file created by configure. If you really mean make the program, as in $ bash: make: not found, then you probably do not have your PATH variable set properly. Copies can be found in /usr/ccs/bin and /usr/xpg4/bin. They are installed with the packages SUNWsprot and SUNWxcu4t respectively (check with pkginfo if they are installed). A copy of GNU's make can also be installed (I think used with amanda) from the Companion CD (CCD). It gets insatlled in /opt/sfw/bin as gmake from package SFWgmake. Sun doesn't supply a C compiler so unless you purchase an extra cost compiler, you will have to install the GNU C compiler (gcc) from the CCD. On a standard installation Sun puts a shell script called cc in /usr/ucb directory; all it does is say is you don't have a compiler. When I install the GNU compilers I then rename /usr/ucb/cc and replace it with a symbolic link to /opt/sfw/bin/gcc. I put similar links in /usr/ccs/bin and /opt/sfw/bin. HTH jon -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Sun Solaris stops compiling
On Thursday 19 August 2004 09:47, Todd Zenker wrote: When I run ./configure --with-user=amanda --with-group=disk, I dont get an error, I get a command prompt right after the config.status: executing depfiles commands. It looks like I can start to run make, but there is no make to run. I know this is a simple thing becuase a ran into the same problem a long long time ago and don't remember what I did... I'm getting to old to remember what I did last week. Join the crowd Todd, I'll be 70 in 6 weeks. My shell is BASH. I put almost every path I can thin of the script would use. Not sure what else. One thing I do is use a script to configure and make amanda. I post it occasionally, and it looks something like this (verify that the compiler tools are included in your $PATH too of course) #!/bin/sh # since I'm always forgetting to su amanda... if [ `whoami` != 'amanda' ]; then echo echo Warning echo Amanda needs to be configured and built by the user amanda, echo but must be installed by user root. echo exit 1 fi make clean rm -f config.status config.cache ./configure --with-user=amanda \ --with-group=disk \ --with-owner=amanda \ --with-tape-device=/dev/nst0 \ --with-changer-device=/dev/sg1 \ --with-gnu-ld --prefix=/usr/local \ --with-debugging=/tmp/amanda-dbg/ \ --with-tape-server=coyote.coyote.den \ --with-amandahosts \ --with-configdir=/usr/local/etc/amanda make clip it, set the execute bits, and edit to fit your scenario. The depfiles error/hang says theres something wrong with the $PATH or the permissions of whats in the $PATH to me, sitting here making SWAG's about others problems (about which I've been shown to not have a clue from time to time :-( ). Any more ideas??? Let me know Thanks Todd On Thu, 19 Aug 2004 12:37:16 +0200, Paul Bijnens [EMAIL PROTECTED] wrote: todd zenker wrote: I'm trying to compile the amanda-2.4.4.p1 client on Solaris 9 and it stops at config.status: executing depfiles commands. Define stop. Any message? Does it simply hang? For how long did you wait? Do you get a shell prompt back? After how long? Is the program waiting for some unresponsive network filesystems? If you're compiling anyway, why did you choose an old version? Current stable is 2.4.4p3. I have had problems with this old version until now. hahahehe... Does configure of other programs (e.g. gnutar) behave the same? Any ideas what I need to do??? More coffee? And that occasionally helps... -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.24% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
RE: Sun Solaris stops compiling
Paul Bijnens said: todd zenker wrote: I'm trying to compile the amanda-2.4.4.p1 client on Solaris 9 and it stops at config.status: executing depfiles commands. If you're compiling anyway, why did you choose an old version? Current stable is 2.4.4p3. Todd - Definitely get 2.4.4p3, 2.4.4p1 on Solaris is unable to find the readline include files even if you give the location to configure. (If you MUST use 2.4.4p1, link /usr/local/include/readline to amanda-2.4.4p1/common-src/readline.) 2.4.4p3 is NOT available at ftp.amanda.org, but it is available via HTTP. (Is there someone on this list who can fix that BTW?) For client only, I compile with --with-user=amanda --with-group=sysadmin --with-smbclient=/usr/local/bin/smbclient --with-gnutar=/usr/local/bin/tar --with-libraries=/tmp/lib --with-include=/tmp/include --without-server --without-restore I like to use /tmp/lib and /tmp/include instead of /usr/local/[lib|include] when compiling because I build packages for distribution to 20+ hosts and it helps me manage dependancies. 2.4.4p3 compiles fine for me on Solaris 9 - I'm compiling my client today actually. I could probably send you a client package for p1 or p3 in Solaris package format - although the p1 would have group=sysadmin and the p3 package wouldn't be tested yet. To compile or run on Solaris, you will also need SUNWgzip (preferable over the Sunfreeware gzip), SMCreadl (or compile the GNU readline libraries yourself), and libgcc if you use gcc. Jon LaBadie said: You say there is no make to run. Do you really mean make or no makefile (or Makefile)? One is a program that must be installed as a system developer utility, the other is the control file created by configure. If you really mean make the program, as in $ bash: make: not found, then you probably do not have your PATH variable set properly. Copies can be found in /usr/ccs/bin and /usr/xpg4/bin. They are installed with the packages SUNWsprot and SUNWxcu4t respectively (check with pkginfo if they are installed). A copy of GNU's make can also be installed (I think used with amanda) from the Companion CD (CCD). It gets insatlled in /opt/sfw/bin as gmake from package SFWgmake. If you are compiling anything on Solaris, you pretty much need to have /usr/ccs/bin in your path. Sun doesn't supply a C compiler so unless you purchase an extra cost compiler, you will have to install the GNU C compiler (gcc) from the CCD. On a standard installation Sun puts a shell script called cc in /usr/ucb directory; all it does is say is you don't have a compiler. When I install the GNU compilers I then rename /usr/ucb/cc and replace it with a symbolic link to /opt/sfw/bin/gcc. I put similar links in /usr/ccs/bin and /opt/sfw/bin. I'd highly recommend against removing the existing /usr/ucb/cc, because it can lead to confusion about which compiler you are using and there are a number of cases where it matters whether you use the Sun compilier or gcc (particularly when building perl modules). Also, Sun may replace /usr/ucb/cc with a patch or upgrade and when you remove an individual file that is part of a package, you've essentially broken your package database. I prefer to set CC=gcc in my .profile/.cshrc and then always use make to compile even if all I use is the default rules. (touch Makefile; make foo or make -f /dev/null foo will compile foo.c into a binary called foo when compiling something too simple to need a Makefile) Julie
Re: Sun Solaris stops compiling
On Thursday 19 August 2004 16:20, BAUMLER Julie L wrote: Paul Bijnens said: todd zenker wrote: I'm trying to compile the amanda-2.4.4.p1 client on Solaris 9 and it stops at config.status: executing depfiles commands. If you're compiling anyway, why did you choose an old version? Current stable is 2.4.4p3. Todd - Definitely get 2.4.4p3, 2.4.4p1 on Solaris is unable to find the readline include files even if you give the location to configure. (If you MUST use 2.4.4p1, link /usr/local/include/readline to amanda-2.4.4p1/common-src/readline.) 2.4.4p3 is NOT available at ftp.amanda.org, but it is available via HTTP. (Is there someone on this list who can fix that BTW?) The http site is a link near the bottom of the home page for amanda.org, and leads to Jean-Louis M's page at umontreal.edu. Not hard to find at all, and quite bookmarkable for later accesses. For client only, I compile with --with-user=amanda --with-group=sysadmin --with-smbclient=/usr/local/bin/smbclient --with-gnutar=/usr/local/bin/tar --with-libraries=/tmp/lib --with-include=/tmp/include --without-server --without-restore I like to use /tmp/lib and /tmp/include instead of /usr/local/[lib|include] when compiling because I build packages for distribution to 20+ hosts and it helps me manage dependancies. 2.4.4p3 compiles fine for me on Solaris 9 - I'm compiling my client today actually. I could probably send you a client package for p1 or p3 in Solaris package format - although the p1 would have group=sysadmin and the p3 package wouldn't be tested yet. To compile or run on Solaris, you will also need SUNWgzip (preferable over the Sunfreeware gzip), SMCreadl (or compile the GNU readline libraries yourself), and libgcc if you use gcc. Jon LaBadie said: You say there is no make to run. Do you really mean make or no makefile (or Makefile)? One is a program that must be installed as a system developer utility, the other is the control file created by configure. If you really mean make the program, as in $ bash: make: not found, then you probably do not have your PATH variable set properly. Copies can be found in /usr/ccs/bin and /usr/xpg4/bin. They are installed with the packages SUNWsprot and SUNWxcu4t respectively (check with pkginfo if they are installed). A copy of GNU's make can also be installed (I think used with amanda) from the Companion CD (CCD). It gets insatlled in /opt/sfw/bin as gmake from package SFWgmake. If you are compiling anything on Solaris, you pretty much need to have /usr/ccs/bin in your path. Sun doesn't supply a C compiler so unless you purchase an extra cost compiler, you will have to install the GNU C compiler (gcc) from the CCD. On a standard installation Sun puts a shell script called cc in /usr/ucb directory; all it does is say is you don't have a compiler. When I install the GNU compilers I then rename /usr/ucb/cc and replace it with a symbolic link to /opt/sfw/bin/gcc. I put similar links in /usr/ccs/bin and /opt/sfw/bin. I'd highly recommend against removing the existing /usr/ucb/cc, because it can lead to confusion about which compiler you are using and there are a number of cases where it matters whether you use the Sun compilier or gcc (particularly when building perl modules). Also, Sun may replace /usr/ucb/cc with a patch or upgrade and when you remove an individual file that is part of a package, you've essentially broken your package database. I prefer to set CC=gcc in my .profile/.cshrc and then always use make to compile even if all I use is the default rules. (touch Makefile; make foo or make -f /dev/null foo will compile foo.c into a binary called foo when compiling something too simple to need a Makefile) Julie -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.24% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
Compression apparently ALWAYS happening as --best *AND* on tape host/server!!!!
just gettign amanda going on a new install and from what i can tell, the dang thing is ALWAYS running compression server side, and in --best mode DESPITE the dumptypes defining compression to be done on the clients, and in --fast! The tape host really does not have the CPU to do this i'll include relevant amanda.conf snippets if wanted. (output of pstree below that shows the gzip children...) | | `-amdump,26032 /usr/sbin/amdump MWDaily1 | | `-driver,26041 MWDaily1 | | |-dumper,26043 MWDaily1 | | |-dumper,26044 MWDaily1 | | | `-gzip,26826 --best | | |-dumper,26045 MWDaily1 | | |-dumper,26046 MWDaily1 | | | `-gzip,26686 --best | | |-dumper,26047 MWDaily1 | | |-dumper,26048 MWDaily1 | | |-dumper,26049 MWDaily1 | | |-dumper,26050 MWDaily1 | | `-taper,26042 MWDaily1 | | `-taper,26051 MWDaily1 -- Undocumented Features quote of the moment... It's not the one bullet with your name on it that you have to worry about; it's the twenty thousand-odd rounds labeled `occupant.' --Murphy's Laws of Combat
