subject:"Re\: Problems with amrecover"

Re: problems using amrecover with changer

2009-07-10 Thread Andreas Kuntzagk


Jean-Louis Martineau wrote:

Andreas Kuntzagk wrote:

Hi,

I'm trying to do a (test) recovery using our SL24 changer.
I set amrecover_changer and use setdevice but still get an error 
message when trying to extract files.
Could the reason be that I did the dumps before setting 
amrecover_changer ?

no.

Look for message in the amidxtaped.*.debug file on the tape server.


Ok, this is probably the reason:

1247236826.477475: amidxtaped: changer:  error Fatal error from 
changer script: none Could not run mtx binary at 'mtx'


The mtx binary is at /opt/csw/sbin/mtx so it's probably not in the PATH 
used by the recovery. But it is in the PATH of the amandabackup user.

So where should I set this?



Jean-Louis


Here is my amanda.conf:
==
logdir   /etc/opt/amanda/daily/log# log directory
infofile /etc/opt/amanda/daily/curinfo# database filename
indexdir /etc/opt/amanda/daily/index  # index directory
tapelist /etc/opt/amanda/daily/tapelist   # list of used tapes

usetimestamps 1
tapecycle 18
runtapes 3
#send-amreport-on never

amrecover_changer changer

define tapetype HP-LTO4 {
   comment LTO4 Tapes, values produced by amtapetype, Compression Off
   length 772096 mbytes
   filemark 0 kbytes
   speed 100612 kps
}

tapetype HP-LTO4

tpchanger chg-zd-mtx
changerdev /dev/scsi/changer/c8t500110A00094F7C0d0
tapedev tape:/dev/rmt/0
changerfile /etc/opt/amanda/daily/changer.conf

holdingdisk zfs {
directory /data/backup/daily
}

define dumptype global {
record yes
index yes
auth bsdtcp
program GNUTAR
}


and here the amrecover session:


amrecover setdevice -h fileserver07 changer
Using tape changer from server fileserver07.
amrecover extract
Extract list empty - No files to extract!
amrecover add proteome
Added dir /proteome/ at date 2009-06-25-13-49-29
Added dir /proteome/ at date 2009-06-30-10-01-43
Added dir /proteome/ at date 2009-07-02-10-48-40
Added dir /proteome/ at date 2009-07-03-10-51-17
amrecover extract

Extracting files using tape drive changer on host fileserver07.
The following tapes are needed: test019
test021
test004
test005

Restoring files into directory /data/test
Continue [?/Y/n]?

Extracting files using tape drive changer on host fileserver07.
Load tape test019 now
Continue [?/Y/n/s/d]?
Volume labeled 'test019' not found.
Load tape test019 now
Continue [?/Y/n/d]?

==

regards, Andreas

Re: problems using amrecover with changer

2009-07-10 Thread Jean-Louis Martineau


Edit chg-lib.sh and set MTX to the full path:
MTX=/opt/csw/sbin/mtx

Jean-Louis

Andreas Kuntzagk wrote:

Jean-Louis Martineau wrote:

Andreas Kuntzagk wrote:

Hi,

I'm trying to do a (test) recovery using our SL24 changer.
I set amrecover_changer and use setdevice but still get an error 
message when trying to extract files.
Could the reason be that I did the dumps before setting 
amrecover_changer ?

no.

Look for message in the amidxtaped.*.debug file on the tape server.


Ok, this is probably the reason:

1247236826.477475: amidxtaped: changer:  error Fatal error from 
changer script: none Could not run mtx binary at 'mtx'


The mtx binary is at /opt/csw/sbin/mtx so it's probably not in the 
PATH used by the recovery. But it is in the PATH of the amandabackup 
user.

So where should I set this?



Jean-Louis


Here is my amanda.conf:
==
logdir   /etc/opt/amanda/daily/log# log directory
infofile /etc/opt/amanda/daily/curinfo# database filename
indexdir /etc/opt/amanda/daily/index  # index directory
tapelist /etc/opt/amanda/daily/tapelist   # list of used tapes

usetimestamps 1
tapecycle 18
runtapes 3
#send-amreport-on never

amrecover_changer changer

define tapetype HP-LTO4 {
   comment LTO4 Tapes, values produced by amtapetype, Compression Off
   length 772096 mbytes
   filemark 0 kbytes
   speed 100612 kps
}

tapetype HP-LTO4

tpchanger chg-zd-mtx
changerdev /dev/scsi/changer/c8t500110A00094F7C0d0
tapedev tape:/dev/rmt/0
changerfile /etc/opt/amanda/daily/changer.conf

holdingdisk zfs {
directory /data/backup/daily
}

define dumptype global {
record yes
index yes
auth bsdtcp
program GNUTAR
}


and here the amrecover session:


amrecover setdevice -h fileserver07 changer
Using tape changer from server fileserver07.
amrecover extract
Extract list empty - No files to extract!
amrecover add proteome
Added dir /proteome/ at date 2009-06-25-13-49-29
Added dir /proteome/ at date 2009-06-30-10-01-43
Added dir /proteome/ at date 2009-07-02-10-48-40
Added dir /proteome/ at date 2009-07-03-10-51-17
amrecover extract

Extracting files using tape drive changer on host fileserver07.
The following tapes are needed: test019
test021
test004
test005

Restoring files into directory /data/test
Continue [?/Y/n]?

Extracting files using tape drive changer on host fileserver07.
Load tape test019 now
Continue [?/Y/n/s/d]?
Volume labeled 'test019' not found.
Load tape test019 now
Continue [?/Y/n/d]?

==

regards, Andreas

Re: problems using amrecover with changer

2009-07-10 Thread Jean-Louis Martineau


Andreas Kuntzagk wrote:

Hi,

I'm trying to do a (test) recovery using our SL24 changer.
I set amrecover_changer and use setdevice but still get an error 
message when trying to extract files.
Could the reason be that I did the dumps before setting 
amrecover_changer ?

no.

Look for message in the amidxtaped.*.debug file on the tape server.

Jean-Louis


Here is my amanda.conf:
==
logdir   /etc/opt/amanda/daily/log# log directory
infofile /etc/opt/amanda/daily/curinfo# database filename
indexdir /etc/opt/amanda/daily/index  # index directory
tapelist /etc/opt/amanda/daily/tapelist   # list of used tapes

usetimestamps 1
tapecycle 18
runtapes 3
#send-amreport-on never

amrecover_changer changer

define tapetype HP-LTO4 {
   comment LTO4 Tapes, values produced by amtapetype, Compression Off
   length 772096 mbytes
   filemark 0 kbytes
   speed 100612 kps
}

tapetype HP-LTO4

tpchanger chg-zd-mtx
changerdev /dev/scsi/changer/c8t500110A00094F7C0d0
tapedev tape:/dev/rmt/0
changerfile /etc/opt/amanda/daily/changer.conf

holdingdisk zfs {
directory /data/backup/daily
}

define dumptype global {
record yes
index yes
auth bsdtcp
program GNUTAR
}


and here the amrecover session:


amrecover setdevice -h fileserver07 changer
Using tape changer from server fileserver07.
amrecover extract
Extract list empty - No files to extract!
amrecover add proteome
Added dir /proteome/ at date 2009-06-25-13-49-29
Added dir /proteome/ at date 2009-06-30-10-01-43
Added dir /proteome/ at date 2009-07-02-10-48-40
Added dir /proteome/ at date 2009-07-03-10-51-17
amrecover extract

Extracting files using tape drive changer on host fileserver07.
The following tapes are needed: test019
test021
test004
test005

Restoring files into directory /data/test
Continue [?/Y/n]?

Extracting files using tape drive changer on host fileserver07.
Load tape test019 now
Continue [?/Y/n/s/d]?
Volume labeled 'test019' not found.
Load tape test019 now
Continue [?/Y/n/d]?

==

regards, Andreas

Re: Problems with amrecover in 2.4.5p1

2006-02-21 Thread Paul Bijnens


On 2006-02-21 09:25, Stephen Carville wrote:
My attempt to restore files with amrecover keep failing since I upgraded 
to 2.4.5.  The output in amidxtaped.debug looks like:


amidxtaped: debug 1 pid 14962 ruid 250 euid 250: start at Mon Feb 20 

[...]

amrestore: could not open /dev/ait2: Permission denied
amidxtaped: time 0.004: amrestore terminated normally with status: 2
amidxtaped: time 0.004: rewinding tape ...
amidxtaped: time 0.004: tape_rewind: tape open: /dev/ait2: Permission 
denied

amidxtaped: time 0.005: pid 14962 finish time Mon Feb 20 20:33:06 2006


My first question then is, what are the permissions of /dev/ait2,
and what are the user/group you are using for starting amidxtaped in
(x)inetd.




This makes no sense to me since I was able to recover the files using 
amrestore on the server.


amrestore runs as root, but amidxtaped runs as amanda usually.
If the permissions of /dev/ait2 are group readable, maybe you need
to add groups = yes in xinetd.conf to enable the additional groups
that user amanda is in.


--
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: Problems with amrecover in 2.4.5p1

2006-02-21 Thread Stephen Carville


Paul Bijnens wrote:

On 2006-02-21 09:25, Stephen Carville wrote:

My attempt to restore files with amrecover keep failing since I 
upgraded to 2.4.5.  The output in amidxtaped.debug looks like:


amidxtaped: debug 1 pid 14962 ruid 250 euid 250: start at Mon Feb 20 


[...]


amrestore: could not open /dev/ait2: Permission denied
amidxtaped: time 0.004: amrestore terminated normally with status: 2
amidxtaped: time 0.004: rewinding tape ...
amidxtaped: time 0.004: tape_rewind: tape open: /dev/ait2: Permission 
denied

amidxtaped: time 0.005: pid 14962 finish time Mon Feb 20 20:33:06 2006



My first question then is, what are the permissions of /dev/ait2,
and what are the user/group you are using for starting amidxtaped in
(x)inetd.


Sound of palm slapping forhead...That was it.

/dev/ait2 is a symlink to /dev/nst0.  I checked the old server and the 
permissions there were:


crw-rw-r--1 root disk   9, 128 Aug 30  2001 /dev/nst0

On the new server:

crw-rw  1 root disk 9, 128 Feb 19 11:53 /dev/nst0

Once I added the global read, amrecover worked again.  I don't know how 
many time I looked at those permissions wihtseeing the problem.


Thanks

--
Stephen Carville -- polluting the ranks of skeptics since 1995.
---
Government is actually the worst failure of civilized man. There has 
never been a really good one, and even those that are most tolerable are 
arbitrary, cruel, grasping and unintelligent.

 -- H. L. Mencken

Re: Problems with amrecover, no error messages

2004-11-22 Thread Jon LaBadie

On Mon, Nov 22, 2004 at 11:17:27AM +0100, Sylvia Gelman wrote:
 Hi,
 
 I had similar Problems to Toralf Lund (13.10.2004), after setting chunksize 
 to 1GB it seems ok and I didn´t get anymore the following error messages:
 
 invalid sparse archive member
 tar: Skipping to next header
 
 But unfortunatly I can´t recover any file and I don´t get any error 
 messages. Really strange ...
 Hope someone can help. Please ask if you need more details.
 
 Thanks for any help
 
 Sylvia
 
 P.S. By the way what means the WARNING: not on root of selected filesystem, 
 check man-page! ?
 
 client2:/var/lib/mysql # /usr/sbin/amrecover bac -s srv -t srv -d 
 /dev/rmt/0n
 AMRECOVER Version 2.4.4p1. Contacting server on srv ...
 220 srv AMANDA index server (2.4.4p3) ready.
 200 Access OK
 Setting restore date to today (2004-11-22)
 200 Working date set to 2004-11-22.
 Scanning /export/opt/hold...
 Scanning /hold...
 200 Config set to bac.
 200 Dump host set to client2.
 Trying disk /var ...
 $CWD '/var/lib/mysql' is on disk '/var' mounted at '/var'.
 200 Disk set to /var.
 /var/lib/mysql
 WARNING: not on root of selected filesystem, check man-page!
 amrecover setdate 2004-11-21
 200 Working date set to 2004-11-21.
 amrecover sethost client2
 200 Dump host set to client2.
 amrecover setdisk /var
 200 Disk set to /var.
 amrecover cd lib/mysql
 /var/lib/mysql
 amrecover add fulldump.sql.040930
 Added /lib/mysql/fulldump.sql.040930
 amrecover lpwd
 /var/lib/mysql
 amrecover extract
 
 Extracting files using tape drive /dev/rmt/0n on host srv.
 The following tapes are needed: bac-012
 
 Restoring files into directory /var/lib/mysql
 Continue [?/Y/n]? Y
 
 Extracting files using tape drive /dev/rmt/0n on host srv.
 Load tape bac-012 now
 Continue [?/Y/n/s/t]? Y
 ./lib/mysql/fulldump.sql.040930
 amrecover quit
 200 Good bye.
 
 client2: more /tmp/amanda/amrecover.20041122104426.debug
 -snip-
 cd_glob (lib/mysql) - ^lib/mysql$
 add_dir_list_item: Adding 2004-11-21 0 bac-012 5 /lib/mysql/.
 add_dir_list_item: Adding 2004-11-21 0 bac-012 5 /lib/mysql/demo/
 add_dir_list_item: Adding 2004-11-21 0 bac-012 5 
 /lib/mysql/fulldump.sql
 add_dir_list_item: Adding 2004-11-21 0 bac-012 5 
 /lib/mysql/fulldump.sql.040930
 -snip-
 add_glob (fulldump.sql.040930) - ^fulldump\.sql\.040930$
 add_file: Looking for fulldump\.sql\.040930[/]*$
 add_file: Converted path=fulldump\.sql\.040930[/]*$ to 
 path_on_disk=\/lib\/mysql/fulldump\.sql\.040930[/]*$
 add_file: Pondering ditem-path=/lib/mysql/.
 add_file: Pondering ditem-path=/lib/mysql/demo/
 add_file: Pondering ditem-path=/lib/mysql/fulldump.sql
 add_file: Pondering ditem-path=/lib/mysql/fulldump.sql.040930
 add_file: (Successful) Added /lib/mysql/fulldump.sql.040930
 -snip-
 amrecover: stream_client_privileged: connected to 130.83.28.5.10083
 amrecover: stream_client_privileged: our side is 0.0.0.0.563
 amrecover: try_socksize: receive buffer size is 65536
 Exec'ing /bin/tar with arguments:
 tar
 -xpGvf
 -
 ./lib/mysql/fulldump.sql.040930
 amrecover: pid 15478 finish time Mon Nov 22 10:54:13 2004
 

Sorry for not chopping things down.
It looks to me like things worked as they should
but that your expectations were not accurate.

Suppose I have a disk-list entry (DLE) of /foo/bar,
the bar directory is the root of my DLE
(amrestore calls it a filesystem).

Suppose I want to recover a file /foo/bar/proj/abc/target,
that file gets backed up as ./proj/abc/target relative
to the root of my DLE.

However, it comes back from the recovery relative to
WHATEVER directory you run amrecover from.  I typically
run amrecover from a newly created directory, such as
/tmp/recover.  In that case, the file will recover to
/tmp/recover/proj/abc/target, not under /foo/bar.  If
I really wanted it back in the original place I would
have to run amrecover from /foo/bar.  I don't like to
do that because a human error might trash other things.
I like to recover first, then copy to real destination.

I looks like you ran amrecover from the mysql directory:

 client2:/var/lib/mysql # /usr/sbin/amrecover bac -s srv -t srv -d 

But your DLE was /var:

 Trying disk /var ...
 $CWD '/var/lib/mysql' is on disk '/var' mounted at '/var'.
 200 Disk set to /var.
 /var/lib/mysql
 WARNING: not on root of selected filesystem, check man-page!

Thus, you were not at the root of the selected DLE:

Then you asked to recover /var/lib/mysql/fulldump.sql.040930

 amrecover add fulldump.sql.040930

And it seems to have been recovered:

 Continue [?/Y/n/s/t]? Y
 ./lib/mysql/fulldump.sql.040930

But, because you were not in /var, but in /var/lib/mysql,
it probably came back as /var/lib/mysql/lib/mysql/fulldump.sql.040930.
  ^^^

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: Problems with amrecover, no error messages

2004-11-22 Thread Sylvia Gelman

Hi Jon,
first of all, many thanks for your answer. I was so confused that I even didn´t try a
stupid find over the maschine. Ok, ... I found the file. My error in reasoning was that I
thought I can change in the directory where to recover to after running amrecover with lcd.

Thank you very much for your help!
Sylvia
Sorry for not chopping things down.
It looks to me like things worked as they should
but that your expectations were not accurate.
Suppose I have a disk-list entry (DLE) of /foo/bar,
the bar directory is the root of my DLE
(amrestore calls it a filesystem).
Suppose I want to recover a file /foo/bar/proj/abc/target,
that file gets backed up as ./proj/abc/target relative
to the root of my DLE.
However, it comes back from the recovery relative to
WHATEVER directory you run amrecover from. I typically
run amrecover from a newly created directory, such as
/tmp/recover. In that case, the file will recover to
/tmp/recover/proj/abc/target, not under /foo/bar. If
I really wanted it back in the original place I would
have to run amrecover from /foo/bar. I don't like to
do that because a human error might trash other things.
I like to recover first, then copy to real destination.
I looks like you ran amrecover from the mysql directory:

client2:/var/lib/mysql # /usr/sbin/amrecover bac -s srv -t srv -d

But your DLE was /var:

Trying disk /var ...
$CWD '/var/lib/mysql' is on disk '/var' mounted at '/var'.
200 Disk set to /var.
/var/lib/mysql
WARNING: not on root of selected filesystem, check man-page!

Thus, you were not at the root of the selected DLE:
Then you asked to recover /var/lib/mysql/fulldump.sql.040930

amrecover add fulldump.sql.040930

And it seems to have been recovered:

Continue [?/Y/n/s/t]? Y
./lib/mysql/fulldump.sql.040930

But, because you were not in /var, but in /var/lib/mysql,
it probably came back as /var/lib/mysql/lib/mysql/fulldump.sql.040930.
^^^
--
Sylvia Gelman Telefon: 06151-16-5261
TU-DarmstadtTelefax: 06151-16-2507
Institut fuer Automatisierungstechnik - IAT
FG Regelungstheorie und Robotik
Raum S3|10 529 Email:[EMAIL PROTECTED]
Landgraf-Georg-Str. 4 Systemadministratorin
64283 Darmstadt

Re: Problems using amrecover

2004-05-27 Thread Paul Bijnens

Thorsten Bremer wrote:
schatten:/etc# amrecover Weekly
AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
220 schatten AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2004-05-27)
200 Working date set to 2004-05-27.
200 Working date set to 2004-05-27.
amrecover: Unexpected server end of file
Both server and client are on the same machine, a normal backup is
going without any problem. As amrecover said, everything is
localhost :-)
I found this note in the FAQ:
http://amanda.sourceforge.net/fom-serve/cache/173.html
I tried all in there, I can ping to and from localhost :-) and
nslookup tell me, that localhost is really 127.0.0.1 and vice versa
:-) Because a normal backup is working, I think that access-rights and
so on must be correct.
You didn't try enough:
The FAQ says:
CAUSE: In UNIX / Windows mixed environments could happen that the DNS
and WINS become misaligned.
If this happens, the Reverse Lookup that Amanda Server performs at every
Client connection simply fails and the connection does not establish
returning the error Unexpected server end of file.
Your localhost is actually called schatten, and I guess that a
dns lookup of schatten does not result in localhost, nor in 127.0.0.1.
Don't use localhost in disklist.  It will bit you.
If you don't believe me, just just got bitten...
--
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: Problems using amrecover

2004-05-27 Thread Thorsten Bremer

Moin Paul,

 Your localhost is actually called schatten, and I guess that a
 dns lookup of schatten does not result in localhost, nor in 127.0.0.1.

Hmm... you're right :-)

 Don't use localhost in disklist.  It will bit you.
 If you don't believe me, just just got bitten...

OK, I begin to understand... Any chance to resolve this situation
here?

I tried to re-manage all here: My domain at home is called magnus
(instead of something else, part of history, but this shouldn't affect
the problem, because DNS works well with that :-), so nslookup will
say:

Name:   schatten.magnus
Address: 10.10.10.1

1.10.10.10.in-addr.arpa name = schatten.magnus.

So, correct until here.


/etc/amandahosts:
schatten.magnus root
schatten root


disklist:
schatten.magnus /home/thoddi comp-user-tar


amcheck without any errors after renaming the localhost-dir in
curinfo and index (because they are the same, just hostnames
changed :-)


But:

schatten:~# amrecover Weekly -s schatten.magnus
AMRECOVER Version 2.4.2p2. Contacting server on schatten.magnus ...
220 schatten AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2004-05-27)
200 Working date set to 2004-05-27.
200 Working date set to 2004-05-27.
amrecover: Unexpected server end of file

#ß=(%*'-GRMPF-§§$)='_::-)

Why he told me 200 Access OK first and will fail an few lines
after?

Syslog only said:
May 27 17:06:16 schatten amindexd[11901]: connect from 10.10.10.1


I first thougt about iptables blocking the connection, but the
packetfilter is working correct.


Is the backup gone away? No way to recover it?

-- 
Bis denne,
Thoddi

Re: Problems using amrecover

2004-05-27 Thread Paul Bijnens

Thorsten Bremer wrote:
schatten:~# amrecover Weekly -s schatten.magnus
AMRECOVER Version 2.4.2p2. Contacting server on schatten.magnus ...
220 schatten AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2004-05-27)
200 Working date set to 2004-05-27.
200 Working date set to 2004-05-27.
amrecover: Unexpected server end of file
#ß=(%*'-GRMPF-§§$)='_::-)
My german is very bad :-)
Any clue in the debug file on the server named 
/tmp/amanda/amindexd.XXX.debug ?


Is the backup gone away? No way to recover it?
There is always amrestore, or even dd and tar/restore.

--
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  *
***

52 matches

Mail list logo