Re: Off-Topic: gmail problems with the list
On Thursday 16 February 2006 13:35, Guy Dallaire wrote: >Does anyone here use gmail to receive messages from mailing lists >(like amanda-users) and know of a way to reply automatically to the >list when you answer a question, instead of replying to the poster ? > >Could the list insert it's e-mail address in the "reply-to" header of >it's messages ? Otherwise, when there's nothing, I thing gmail uses >the Original poster's email adress for the reply to. > >Or is there a better way ? > >Thanks I'm not sure if there is or not for gmail. I get it direct from the list here, and kmail usually just does it right if I don't linger on the click for reply too long. It brings up a how do you want to do this after about 1 second. Here, I suck mail from vz's server with fetchmail, and its MDA is set to procmail, procmail runs it by spamassassin and stuffs it into /var/spool/mail/user, then kmail gets it from there to its local boxes sorting them as it moves them. Quasi-complex, but it takes the mail fetching time away from kmail, which is not well threaded & hangs if the far end is slow. -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: Off-Topic: gmail problems with the list
On Thu, Feb 16, 2006 at 03:17:36PM -0700, Donald Murray, P.Eng. wrote: > On 2/16/06, Mitch Collinsworth <[EMAIL PROTECTED]> wrote: > > > > On Thu, 16 Feb 2006, Guy Dallaire wrote: > > > > > Could the list insert it's e-mail address in the "reply-to" header of > > > it's messages ? > > > > Hack the list to work around a missing feature in your e-mail client? > > Please, no. > > > > > Otherwise, when there's nothing, I thing gmail uses > > > the Original poster's email adress for the reply to. > > > > Is there really no reply-all function? If not then you should find a > > better e-mail client. > > > > -Mitch > > > > Gmail does supply a reply-to-all button. You just have to remember to use > that instead of the reply button. And you have to remember not to top-post. > ;-) And you will probably have to delete the OP's address from the "all" list. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Off-Topic: gmail problems with the list
On 2/16/06, Mitch Collinsworth <[EMAIL PROTECTED]> wrote: > > On Thu, 16 Feb 2006, Guy Dallaire wrote: > > > Could the list insert it's e-mail address in the "reply-to" header of > > it's messages ? > > Hack the list to work around a missing feature in your e-mail client? > Please, no. > > > Otherwise, when there's nothing, I thing gmail uses > > the Original poster's email adress for the reply to. > > Is there really no reply-all function? If not then you should find a > better e-mail client. > > -Mitch > Gmail does supply a reply-to-all button. You just have to remember to use that instead of the reply button. And you have to remember not to top-post. ;-)
Re: Off-Topic: gmail problems with the list
On Thu, 16 Feb 2006, Guy Dallaire wrote: Could the list insert it's e-mail address in the "reply-to" header of it's messages ? Hack the list to work around a missing feature in your e-mail client? Please, no. Otherwise, when there's nothing, I thing gmail uses the Original poster's email adress for the reply to. Is there really no reply-all function? If not then you should find a better e-mail client. -Mitch
Off-Topic: gmail problems with the list
Does anyone here use gmail to receive messages from mailing lists (like amanda-users) and know of a way to reply automatically to the list when you answer a question, instead of replying to the poster ? Could the list insert it's e-mail address in the "reply-to" header of it's messages ? Otherwise, when there's nothing, I thing gmail uses the Original poster's email adress for the reply to. Or is there a better way ? Thanks
Re: Still get ERROR [host fw.my.co.uk: port 62679 not secure] after I added my ipchain rule:
On 02/16/2006 05:02 PM, Chuck Amadi Systems Administrator wrote:
Hi List sorry for the continuous cries for help.
Regarding Amanda and ipchains rules it didn't work Amanda client on server was
still
forking to secure ports that weren't in my udp range. I run tcpdump
port 10080 on server.
ERROR [host firewall.my.co.uk: port 64524 not secure]
So the firewall does NAT (that is why, from the client's point of view,
the ipnumber is the firewall itself, and not the amanda server, and the
portnumber is >6).
So, as already said, you should patch the client amanda software only
for that host (i.e. no need to install that version on any other machine
or amanda server), to disable the check for a udp source port < 1024:
For amanda 2.4.5p1, edit the file common-src/security.c:
You find this section:
229
230 /* next, make sure the remote port is a "reserved" one */
231
232 if(ntohs(addr->sin_port) >= IPPORT_RESERVED) {
233 ap_snprintf(number, sizeof(number), "%d",
ntohs(addr->sin_port));
234 *errstr = vstralloc("[",
235 "host ", remotehost, ": ",
236 "port ", number, " not secure",
237 "]", NULL);
238 amfree(remotehost);
239 return 0;
240 }
and make test test succeed always, by changing line 232:
232 if(1 || ntohs(addr->sin_port) >= IPPORT_RESERVED) {
i.e. add the "1 ||" string to the if statement.
--
Paul Bijnens, xplanation Technology ServicesTel +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, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***
Still get ERROR [host fw.my.co.uk: port 62679 not secure] after I added my ipchain rule:
Hi List sorry for the continuous cries for help. Regarding Amanda and ipchains rules it didn't work Amanda client on server was still forking to secure ports that weren't in my udp range. I run tcpdump port 10080 on server. Then run /usr/sbin/amcheck DailySet1 on tape-server tape server. server output below: tcpdump: listening on eth0 16:41:14.529918 firewall.my.co.uk.64524 > server.my.co.uk.amanda: udp 117 (DF) 16:41:14.537221 server.my.co.uk.amanda > firewall.my.co.uk.64524: udp 50 (DF) 16:41:14.543520 server.my.co.uk.amanda > firewall.my.co.uk.64524: udp 100 (DF) Thus on server less /tmp/amanda/amandad.20060216164114.debug Amanda 2.4 REQ HANDLE 003-D0990808 SEQ 1140104146 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe0f; amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 003-D0990808 SEQ 1140104146 amandad: time 0.006: sending REP packet: Amanda 2.4 REP HANDLE 003-D0990808 SEQ 1140104146 ERROR [host firewall.my.co.uk: port 64524 not secure] It should have forked to the ports in udp port range that I had compiled with the switch --with-udpportrange=1001,1009 . I am still trouble shooting and awaiting info on mailing list. I had edit my firewall and added the following ipchain rules Outgoing mail has no restrictions. 1001 and 1009 is what I used for the udp port range and I use 11000 11030 for tcp port range I am led to believe that this doesn't cause any isses with the ussally amanda ports 10080,10082 and 10083. ipchains -A input -i $EXTERNAL_INTERFACE -p udp -s 193.xx.xx.xxx 1001:1009 -j ACCEPT ipchains -A input -i $EXTERNAL_INTERFACE -p udp -s 193.xx.xx.xxx 10080:10083 -j ACCEPT Any other tips in order to get through the firewall until one day move to iptables. Cheers -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
AW: AW: AW: AW: Question: does this DLT Drive work?
It works. Maybe its normal that there are no sounds when i try to rewind the
tape when its also at the beginning from the tape!
Thank you all for your help
Backup works very well
-Ursprüngliche Nachricht-
Von: George Kelbley [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 16. Februar 2006 16:47
An: Sebastian Koesters
Betreff: Re: AW: AW: AW: Question: does this DLT Drive work?
Well, that looks like it labeled the tape, if you do "amtape config
current" it should read the label and tell you. Where config is your
real config name of course.
Sebastian Koesters wrote:
> Its a new new and (i think) a real good tape.
>
> I tried to label it:
>
> bash-3.00$ amlabel full-sonntag DailySet1001
> rewinding, reading label, reading label: Input/output error
> rewinding, writing label DailySet1001, checking label, done.
>
> My config:
>
> tapedev "/dev/nst0
>
> tapetype DLT320
>
> define tapetype DLT320 {
> comment "DLT 320"
> length 30 mbytes
> filemark 28 kbytes
> speed 2349 kps
> }
>
>
>
> -Ursprüngliche Nachricht-
> Von: George Kelbley [mailto:[EMAIL PROTECTED]
> Gesendet: Donnerstag, 16. Februar 2006 16:25
> An: Sebastian Koesters
> Betreff: Re: AW: AW: Question: does this DLT Drive work?
>
> Yes it should. If send mine a rewind command I can hear it. Besides
> rewind, have tried any other commands, like try to make it seek forward
> using the fsf option in mt?
>
> Is this a new or used tape drive? Is it known to be good?
>
>
> Sebastian Koesters wrote:
>
>>Hi and thank you
>>
>>I see this
>>
>>scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
>>
>>aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
>>
>> Vendor: QUANTUM Model: DLT-V4Rev: 0400
>> Type: Sequential-Access ANSI SCSI revision: 02
>> target0:0:4: Beginning Domain Validation
>>WIDTH IS 1
>>(scsi0:A:4): 6.600MB/s transfers (16bit)
>> target0:0:4: Domain Validation skipping write tests
>>(scsi0:A:4): 40.000MB/s transfers (20.000MHz, offset 96, 16bit)
>> target0:0:4: Ending Domain Validation
>>
>>and this in dmesg
>>
>>st: Version 20050312, fixed bufsize 32768, s/g segs 256
>>Attached scsi tape st0 at scsi0, channel 0, id 4, lun 0
>>st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA
>>1048575
>>
>>so the drive must be /dev/st0
>>
>>but shouldnt the drive make some sound or something like this when i try
>
> to
>
>>rewind (mt -f /dev/st0 rewind) ?!
>>
>>it shows no activity on the led and makes no sounds (using the tape)
>>
>>
>>-Ursprüngliche Nachricht-
>>Von: Paul Bijnens [mailto:[EMAIL PROTECTED]
>>Gesendet: Donnerstag, 16. Februar 2006 16:01
>>An: Sebastian Koesters
>>Betreff: Re: AW: Question: does this DLT Drive work?
>>
>>On 02/16/2006 03:38 PM, Sebastian Koesters wrote:
>>
>>
>>>Now i build in the drive but i do not know whats his device name is?!
>>>
>>>My old DAT-Drive was nst0 but this does nt work with the DLT!?
>>
>>
>>Do "dmesg | less", short after a reboot (short means: when the
>>oldest messages in the kernel ring buffer are not yet overwritten
>>by newer ones, that could be minutes, or months, depending on
>>your environment).
>>
>>Look in the boot messages for your hardware.
>>First a SCSI card should be detected (from my machine:)
>>
>> scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
>>
>> aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
>>
>> (scsi0:A:3): 160.000MB/s transfers (80.000MHz DT, offset 64, 16bit)
>>Vendor: HPModel: Ultrium 2-SCSIRev: S24D
>>Type: Sequential-Access ANSI SCSI revision: 03
>>
>>If you do not see that, you may need to load the kernel module for
>>your particular scsi card. In my case it is done automatically,
>>the manual command would be: "modprobe aic7xxx", because that kernel
>>module can handle that kind of hardware card.
>>
>>Some lines further down, you should see the sequential tape (st)
>>kernel module handle the tape drive that was discovered:
>>
>> st: Version 20040403, fixed bufsize 32768, s/g segs 256
>> Attached scsi tape st0 at scsi0, channel 0, id 3, lun 0
>> st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA
>>1048575
>>
>>If you don't have lines starting with 'st', you may need to load the
>>st-kernel module too (manual command: "modprobe st").
>>
>>The middle line above also show that "st0" (that means /dev/st0) is
>>the tape drive device.
>>
>>A good introduction is found here:
>>
>
>
http://www.chongluo.com/books/rute/node45.html#SECTION004569000
>
>>
>>
>>
>
--
George Kelbley System Support Group
Computer Science Department University of New Mexico
505-277-6502Fax: 505-277-6927
AW: AW: AW: Question: does this DLT Drive work?
Its a new new and (i think) a real good tape.
I tried to label it:
bash-3.00$ amlabel full-sonntag DailySet1001
rewinding, reading label, reading label: Input/output error
rewinding, writing label DailySet1001, checking label, done.
My config:
tapedev "/dev/nst0
tapetype DLT320
define tapetype DLT320 {
comment "DLT 320"
length 30 mbytes
filemark 28 kbytes
speed 2349 kps
}
-Ursprüngliche Nachricht-
Von: George Kelbley [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 16. Februar 2006 16:25
An: Sebastian Koesters
Betreff: Re: AW: AW: Question: does this DLT Drive work?
Yes it should. If send mine a rewind command I can hear it. Besides
rewind, have tried any other commands, like try to make it seek forward
using the fsf option in mt?
Is this a new or used tape drive? Is it known to be good?
Sebastian Koesters wrote:
> Hi and thank you
>
> I see this
>
> scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
>
> aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
>
> Vendor: QUANTUM Model: DLT-V4Rev: 0400
> Type: Sequential-Access ANSI SCSI revision: 02
> target0:0:4: Beginning Domain Validation
> WIDTH IS 1
> (scsi0:A:4): 6.600MB/s transfers (16bit)
> target0:0:4: Domain Validation skipping write tests
> (scsi0:A:4): 40.000MB/s transfers (20.000MHz, offset 96, 16bit)
> target0:0:4: Ending Domain Validation
>
> and this in dmesg
>
> st: Version 20050312, fixed bufsize 32768, s/g segs 256
> Attached scsi tape st0 at scsi0, channel 0, id 4, lun 0
> st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA
> 1048575
>
> so the drive must be /dev/st0
>
> but shouldnt the drive make some sound or something like this when i try
to
> rewind (mt -f /dev/st0 rewind) ?!
>
> it shows no activity on the led and makes no sounds (using the tape)
>
>
> -Ursprüngliche Nachricht-
> Von: Paul Bijnens [mailto:[EMAIL PROTECTED]
> Gesendet: Donnerstag, 16. Februar 2006 16:01
> An: Sebastian Koesters
> Betreff: Re: AW: Question: does this DLT Drive work?
>
> On 02/16/2006 03:38 PM, Sebastian Koesters wrote:
>
>>Now i build in the drive but i do not know whats his device name is?!
>>
>>My old DAT-Drive was nst0 but this does nt work with the DLT!?
>
>
> Do "dmesg | less", short after a reboot (short means: when the
> oldest messages in the kernel ring buffer are not yet overwritten
> by newer ones, that could be minutes, or months, depending on
> your environment).
>
> Look in the boot messages for your hardware.
> First a SCSI card should be detected (from my machine:)
>
> scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
>
> aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
>
> (scsi0:A:3): 160.000MB/s transfers (80.000MHz DT, offset 64, 16bit)
> Vendor: HPModel: Ultrium 2-SCSIRev: S24D
> Type: Sequential-Access ANSI SCSI revision: 03
>
> If you do not see that, you may need to load the kernel module for
> your particular scsi card. In my case it is done automatically,
> the manual command would be: "modprobe aic7xxx", because that kernel
> module can handle that kind of hardware card.
>
> Some lines further down, you should see the sequential tape (st)
> kernel module handle the tape drive that was discovered:
>
> st: Version 20040403, fixed bufsize 32768, s/g segs 256
> Attached scsi tape st0 at scsi0, channel 0, id 3, lun 0
> st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA
> 1048575
>
> If you don't have lines starting with 'st', you may need to load the
> st-kernel module too (manual command: "modprobe st").
>
> The middle line above also show that "st0" (that means /dev/st0) is
> the tape drive device.
>
> A good introduction is found here:
>
http://www.chongluo.com/books/rute/node45.html#SECTION004569000
>
>
>
>
--
George Kelbley System Support Group
Computer Science Department University of New Mexico
505-277-6502Fax: 505-277-6927
Re: AW: Question: does this DLT Drive work?
I'm using debian stable, and when my amanda server boots up my tape
drive is detected as /dev/st0 (and /dev/nst0). Do you still have the
old DAT drive connected? Does the scsi interface detect the hardware?
Should be mesages in dmesg.
Sebastian Koesters wrote:
Hi
Now i build in the drive but i do not know whats his device name is?!
My old DAT-Drive was nst0 but this does nt work with the DLT!?
-Ursprüngliche Nachricht-
Von: George Kelbley [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 9. Februar 2006 16:17
An: Sebastian Koesters
Betreff: Re: Question: does this DLT Drive work?
I use this in an Overland Data Loaderexpress, and it works fine.
I got the tape type off the amanda.org pages.
In my case the tape library has an interface to enable or disable
compression. If you have a standalone tape drive I'm not sure how you
do it.
this the tape type I'm using :
define tapetype SDLT320 {
comment "SDLT 320 drive in OverLand Storage Neo 2000 Library"
length 154753 mbytes
filemark 28 kbytes
speed 2349 kps
}
Sebastian Koesters wrote:
Quantum DLT V4 320 U2W (160GB uncompressed - 320GB compressed)
Does this drive work good with amanda?
How do i have to set it up in amanda.conf?
How do i activate the compression of the drive to get the full 230GB?
Thanks for the Help!
Regards Sebastian
--
George Kelbley System Support Group
Computer Science Department University of New Mexico
505-277-6502Fax: 505-277-6927
AW: AW: Question: does this DLT Drive work?
Hi and thank you I see this scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36 aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs Vendor: QUANTUM Model: DLT-V4Rev: 0400 Type: Sequential-Access ANSI SCSI revision: 02 target0:0:4: Beginning Domain Validation WIDTH IS 1 (scsi0:A:4): 6.600MB/s transfers (16bit) target0:0:4: Domain Validation skipping write tests (scsi0:A:4): 40.000MB/s transfers (20.000MHz, offset 96, 16bit) target0:0:4: Ending Domain Validation and this in dmesg st: Version 20050312, fixed bufsize 32768, s/g segs 256 Attached scsi tape st0 at scsi0, channel 0, id 4, lun 0 st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA 1048575 so the drive must be /dev/st0 but shouldnt the drive make some sound or something like this when i try to rewind (mt -f /dev/st0 rewind) ?! it shows no activity on the led and makes no sounds (using the tape) -Ursprüngliche Nachricht- Von: Paul Bijnens [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 16. Februar 2006 16:01 An: Sebastian Koesters Betreff: Re: AW: Question: does this DLT Drive work? On 02/16/2006 03:38 PM, Sebastian Koesters wrote: > > Now i build in the drive but i do not know whats his device name is?! > > My old DAT-Drive was nst0 but this does nt work with the DLT!? Do "dmesg | less", short after a reboot (short means: when the oldest messages in the kernel ring buffer are not yet overwritten by newer ones, that could be minutes, or months, depending on your environment). Look in the boot messages for your hardware. First a SCSI card should be detected (from my machine:) scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36 aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs (scsi0:A:3): 160.000MB/s transfers (80.000MHz DT, offset 64, 16bit) Vendor: HPModel: Ultrium 2-SCSIRev: S24D Type: Sequential-Access ANSI SCSI revision: 03 If you do not see that, you may need to load the kernel module for your particular scsi card. In my case it is done automatically, the manual command would be: "modprobe aic7xxx", because that kernel module can handle that kind of hardware card. Some lines further down, you should see the sequential tape (st) kernel module handle the tape drive that was discovered: st: Version 20040403, fixed bufsize 32768, s/g segs 256 Attached scsi tape st0 at scsi0, channel 0, id 3, lun 0 st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA 1048575 If you don't have lines starting with 'st', you may need to load the st-kernel module too (manual command: "modprobe st"). The middle line above also show that "st0" (that means /dev/st0) is the tape drive device. A good introduction is found here: http://www.chongluo.com/books/rute/node45.html#SECTION004569000 -- Paul Bijnens, xplanation Technology ServicesTel +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, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
AW: Question: does this DLT Drive work?
Hi
Now i build in the drive but i do not know whats his device name is?!
My old DAT-Drive was nst0 but this does nt work with the DLT!?
-Ursprüngliche Nachricht-
Von: George Kelbley [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 9. Februar 2006 16:17
An: Sebastian Koesters
Betreff: Re: Question: does this DLT Drive work?
I use this in an Overland Data Loaderexpress, and it works fine.
I got the tape type off the amanda.org pages.
In my case the tape library has an interface to enable or disable
compression. If you have a standalone tape drive I'm not sure how you
do it.
this the tape type I'm using :
define tapetype SDLT320 {
comment "SDLT 320 drive in OverLand Storage Neo 2000 Library"
length 154753 mbytes
filemark 28 kbytes
speed 2349 kps
}
Sebastian Koesters wrote:
> Quantum DLT V4 320 U2W (160GB uncompressed - 320GB compressed)
>
> Does this drive work good with amanda?
>
> How do i have to set it up in amanda.conf?
>
> How do i activate the compression of the drive to get the full 230GB?
>
> Thanks for the Help!
>
> Regards Sebastian
>
>
--
George Kelbley System Support Group
Computer Science Department University of New Mexico
505-277-6502Fax: 505-277-6927
Re: AW: Question: does this DLT Drive work?
On 02/16/2006 03:38 PM, Sebastian Koesters wrote: Now i build in the drive but i do not know whats his device name is?! My old DAT-Drive was nst0 but this does nt work with the DLT!? Do "dmesg | less", short after a reboot (short means: when the oldest messages in the kernel ring buffer are not yet overwritten by newer ones, that could be minutes, or months, depending on your environment). Look in the boot messages for your hardware. First a SCSI card should be detected (from my machine:) scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36 aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs (scsi0:A:3): 160.000MB/s transfers (80.000MHz DT, offset 64, 16bit) Vendor: HPModel: Ultrium 2-SCSIRev: S24D Type: Sequential-Access ANSI SCSI revision: 03 If you do not see that, you may need to load the kernel module for your particular scsi card. In my case it is done automatically, the manual command would be: "modprobe aic7xxx", because that kernel module can handle that kind of hardware card. Some lines further down, you should see the sequential tape (st) kernel module handle the tape drive that was discovered: st: Version 20040403, fixed bufsize 32768, s/g segs 256 Attached scsi tape st0 at scsi0, channel 0, id 3, lun 0 st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA 1048575 If you don't have lines starting with 'st', you may need to load the st-kernel module too (manual command: "modprobe st"). The middle line above also show that "st0" (that means /dev/st0) is the tape drive device. A good introduction is found here: http://www.chongluo.com/books/rute/node45.html#SECTION004569000 -- Paul Bijnens, xplanation Technology ServicesTel +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, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: Question: does this DLT Drive work?
On Thu, Feb 16, 2006 at 03:38:35PM +0100, Sebastian Koesters wrote: > Hi > > Now i build in the drive but i do not know whats his device name is?! > > My old DAT-Drive was nst0 but this does nt work with the DLT!? > What have you tried? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Still get ERROR [host fw.my.co.uk: port 62679 not secure] after I added my ipchain rule:
On 02/16/2006 01:39 PM, Chuck Amadi Systems Administrator wrote: Yesterday Someone posted a amadmin command to egrep --with-udpportrange=, So I can check my tape server. Please could you resend the amadmin ConfigName | egrep -i --with-udpportrange=1001,1009 something like that thx. amadmin x version | grep configure without "grep" for more information... I also run the tcpdump port 10080 on the amanda client and then on the amanda tape server on amcheck ConfigName and I could see that the port on my main tape server was 957 which is privileged port. The port was not 1001, 1009 on the amanda tape server. Which seems to imply that another program than then one you compiled was run... But even it would be the right program, the other side sees the packets coming from some port > 6, even if it the source port was 1001 instead of 957. Which is a NAT problem on the firewall, which cannot be solved by recompiling with a stricter udp range. -- Paul Bijnens, xplanation Technology ServicesTel +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, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: Still get ERROR [host fw.my.co.uk: port 62679 not secure] after I added my ipchain rule:
Hi
Yesterday Someone posted a amadmin command to egrep
--with-udpportrange=,
So I can check my tape server.
Please could you resend the amadmin ConfigName | egrep -i
--with-udpportrange=1001,1009
something like that thx.
amadmin {} ...
I also run the tcpdump port 10080 on the amanda client and then on the
amanda tape server on amcheck ConfigName and I could see that the port
on my main tape server was 957 which is privileged port.
The port was not 1001, 1009 on the amanda tape server.
Cheers
On Tue, 2006-02-14 at 17:19 +0100, Paul Bijnens wrote:
> On 02/14/2006 04:56 PM, Chuck Amadi Systems Administrator wrote:
> >
> > I have just edited my firewall and added a ipchain rule but I still got
> > an error as below:
> >
> > Amanda Backup Client Hosts Check
> >
> > ERROR: server.my.co.uk: [host fw.smtl.co.uk: port 62679 not secure]
>
>
> This seems to be a result of the NAT in ipchains:
> it changes the source port to someting over 6.
>
> However, why is the name "fw.smtl.co.uk"? I did not know that
> ipchains used uses NAT for traffic to the firewall itself too?
> Make really really sure that the amandaserver does bind to a port
> from the udp-port range:
>In one window start as root:
># tcpdump port 10080
>
>In another window, to the "amcheck".
> And verify the that port on the amandaserver is one from 1001-1009.
> This could also happen when amcheck lost the suid root bit
> (but I believe that it would complain about that before you get
> that far).
>
> A possible workaround here is to recompile the
> software on the client to not fail on a "non secure" port.
>
> That notion of "secure port" (ports < 1024 require root
> priviledge to open), is in these days not a strong
> security check anyway, where anyone can install a workstation
> or boot from a live-CD and be root to open any port < 1024.
>
>
> > I have setup my fw rules as below:
> >
> > # Amanda Client - Enterprise random udp forks to Nemesis Server
> >
> > ipchains -A input -i $EXTERNAL_INTERFACE -p udp -s 193.XX.XX.XXX
> > 1001:1009 -j ACCEPT
> >
> > ipchains -A input -i $EXTERNAL_INTERFACE -p udp -s 193.XX.XX.XXX
> > 10080:10083 -j ACCEPT
> >
> > Outgoing packets are allowed from behind our firewall and all forwaded
> > to our main file server that is the same server for amanda backup tape
> > server
>
>
> I do not remember anymore, but maybe there is a possibility
> to not do NAT for a certain portrange/host ?
>
>
> >
> > I re compiled amanda client as below:
> >
> > ./configure --with-user=amanda --with-group=disk
> > --with-configdir=/etc/amanda --with-udpportrange=1001, 1009
> > --with-tcpportrange=11000, 11300
>
>
--
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory (SMTL),
Princess of Wales Hospital
Coity Road
Bridgend,
United Kingdom, CF31 1RQ.
Email chuck.smtl.co.uk
Tel: +44 1656 752820
Fax: +44 1656 752830
