Comentários e situações que passam
terça-feira, 31 de março de 2015
Adicionar máquina diferente ao pool xenserver
xe pool-join master-address=10.3.10.15 master-username=root master-password='senha' --force
migrar maquina para outro pool xenserver
xe vm-migrate name-label=maquinaVirtual remote-master=10.3.50.37 remote-username=root remote-password='senha' live=true force=true
Fazer update xenserver
xe patch-upload -s 10.3.50.42 -u root -pw 'senha' file-name=/tmp/updates/XS62E001.xsupdate
xe -s 10.3.50.42 -u root -pw 'senha' patch-pool-apply uuid=dedcc0dd-d8f3-4f76-90ca-92697c7a44f0
xe patch-list -s 10.3.50.42 -u root -pw 'senha' name-label=XS62E001
xe-toolstack-restart
xe -s 10.3.50.42 -u root -pw 'senha' patch-pool-apply uuid=dedcc0dd-d8f3-4f76-90ca-92697c7a44f0
xe patch-list -s 10.3.50.42 -u root -pw 'senha' name-label=XS62E001
xe-toolstack-restart
criar certificado openssl
openssl x509 -inform der -in servicos.crt -out servicosCA.pem
openssl x509 -inform der -in COMODORSAOrganizationValidationSecureServerCA.crt -out servicosCA.pem
openssl x509 -inform der -in COMODORSAAddTrustCA.crt -out servicosCA.pem
openssl x509 -inform der -in AddTrustExternalCARoot.crt -out servicosCA.pem
openssl genrsa -des3 -out sql.key 2048
openssl req -new -key sql.key -out sql.csr
openssl x509 -req -in sql.csr -days 7300 -signkey sql.key -out sql.pem
openssl x509 -in sql.pem -inform PEM -out sql.cer -outform DER
openssl rsa -in sql.pem -outform PVK -pvk-strong -out sql.pvk
openssl rsa -in sql.key -outform PVK -pvk-strong -out sql
openssl x509 -inform der -in COMODORSAOrganizationValidationSecureServerCA.crt -out servicosCA.pem
openssl x509 -inform der -in COMODORSAAddTrustCA.crt -out servicosCA.pem
openssl x509 -inform der -in AddTrustExternalCARoot.crt -out servicosCA.pem
openssl genrsa -des3 -out sql.key 2048
openssl req -new -key sql.key -out sql.csr
openssl x509 -req -in sql.csr -days 7300 -signkey sql.key -out sql.pem
openssl x509 -in sql.pem -inform PEM -out sql.cer -outform DER
openssl rsa -in sql.pem -outform PVK -pvk-strong -out sql.pvk
openssl rsa -in sql.key -outform PVK -pvk-strong -out sql
trocar senha powershell
$computer=Get-WMIObject Win32_ComputerSystem | Select-Object -ExpandProperty name
([ADSI] "WinNT://$computer/administrador").SetPassword("senha")
([ADSI] "WinNT://$computer/administrador").SetPassword("senha")
colocar maquinas dominio powershell
$credential = New-Object System.Management.Automation.PsCredential("MY.DOMAIN.COM\user", (ConvertTo-SecureString "mypassword" -AsPlainText -Force))
Add-Computer -DomainName "MY.DOMAIN.COM" -Credential $credential -OUPath ("OU=Computers,DC=MY,DC=DOMAIN,DC=COM")
Add-Computer -DomainName "MY.DOMAIN.COM" -Credential $credential -OUPath ("OU=Computers,DC=MY,DC=DOMAIN,DC=COM")
restore grub live cd
1. Dê boot pelo LiveCD.
2. No terminal, digite:
$ sudo fdisk -l
Obs.: Note na saída deste comando qual a partição (sdaX) que o Ubuntu está instalado. Sendo X o número desta partição.
3. Então digite os comandos na ordem mostrada (substitua X pela partição do Ubuntu):
$ sudo mount /dev/sdaX /mnt
$ sudo mount --bind /dev/ /mnt/dev
$ sudo chroot /mnt
4. Agora digite:
# update-grub
# grub-install /dev/sda
5. Saia do modo chroot pressionando: Ctrl+d
6. Desmonte as partições:
$ sudo umount /mnt/dev
$ sudo umount /mnt
7. Reinicie seu computador.
Você perceberá que o seu Ubuntu vai abrir, mas sem mostrar opções no GRUB para escolher seu sistema operacional.
8. Para resolver este problema, dentro do Ubuntu instalado, digite:
$ sudo update-grub
2. No terminal, digite:
$ sudo fdisk -l
Obs.: Note na saída deste comando qual a partição (sdaX) que o Ubuntu está instalado. Sendo X o número desta partição.
3. Então digite os comandos na ordem mostrada (substitua X pela partição do Ubuntu):
$ sudo mount /dev/sdaX /mnt
$ sudo mount --bind /dev/ /mnt/dev
$ sudo chroot /mnt
4. Agora digite:
# update-grub
# grub-install /dev/sda
5. Saia do modo chroot pressionando: Ctrl+d
6. Desmonte as partições:
$ sudo umount /mnt/dev
$ sudo umount /mnt
7. Reinicie seu computador.
Você perceberá que o seu Ubuntu vai abrir, mas sem mostrar opções no GRUB para escolher seu sistema operacional.
8. Para resolver este problema, dentro do Ubuntu instalado, digite:
$ sudo update-grub
move /tmp to ram (usar a ram como disco)
RAMTMP=yes /etc/default/tmpfs
mkdir /dev/shm/tmp
chmod 1777 /dev/sdm/tmp
mount --bind /dev/shm/tmp /tmp
tmpfs /tmp tmpfs mode=1777,nosuid,nodev 0 0
mount -o mode=1777,nosuid,nodev -i tmpfs tmpfs /tmp
mkdir /dev/shm/tmp
chmod 1777 /dev/sdm/tmp
mount --bind /dev/shm/tmp /tmp
tmpfs /tmp tmpfs mode=1777,nosuid,nodev 0 0
mount -o mode=1777,nosuid,nodev -i tmpfs tmpfs /tmp
comandos fortinet
diagnose sys top
diag test auth ldap
ldap tet query from the forti to the ad
scp admin@fortinet:sys_config / backup
diagnose sniffer packet any "host 1.1.1.1 and host 1.2.2.2" 4
diag ip address list
diag test auth ldap
ldap tet query from the forti to the ad
scp admin@fortinet:sys_config / backup
diagnose sniffer packet any "host 1.1.1.1 and host 1.2.2.2" 4
diag ip address list
timeout ssh
SSH Client
This method is the way to go if you have no administrator access to the server you are connecting to. This method will apply to all the servers you are connecting to, instead of only to a specific server.
What you're basically to do is to configure your SSH client client to periodically send keep alive message to the SSH server. If you're running Ubuntu / Debian, edit /etc/ssh/ssh_config and set ServerAliveInterval option to the following;
ServerAliveInterval 100
This option is to tell your SSH client to automatically send the keep alive message every 100 seconds to the SSH server, even if you're away from your client machine. The server will assume you're not idling and will not disconnect your session.
SSH server
If you have administrator access to the server, you can configure the ClientAliveInterval, TCPKeepAlive and ClientAliveCountMax options in the SSHd configuration file. If you're running Ubuntu / Debian,
the file's path is /etc/ssh/sshd_config
ClientAliveInterval 30
TCPKeepAlive yes
ClientAliveCountMax 99999
You will need to restart the SSH server for the changes to take effect.
sudo /etc/init.d/sshd restart
This method is the way to go if you have no administrator access to the server you are connecting to. This method will apply to all the servers you are connecting to, instead of only to a specific server.
What you're basically to do is to configure your SSH client client to periodically send keep alive message to the SSH server. If you're running Ubuntu / Debian, edit /etc/ssh/ssh_config and set ServerAliveInterval option to the following;
ServerAliveInterval 100
This option is to tell your SSH client to automatically send the keep alive message every 100 seconds to the SSH server, even if you're away from your client machine. The server will assume you're not idling and will not disconnect your session.
SSH server
If you have administrator access to the server, you can configure the ClientAliveInterval, TCPKeepAlive and ClientAliveCountMax options in the SSHd configuration file. If you're running Ubuntu / Debian,
the file's path is /etc/ssh/sshd_config
ClientAliveInterval 30
TCPKeepAlive yes
ClientAliveCountMax 99999
You will need to restart the SSH server for the changes to take effect.
sudo /etc/init.d/sshd restart
win8 tela resolucao app
Navegue até encontrar as chaves abaixo abaixo:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E 968-E325-11CE-BFC1-08002BE10318}000
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E 968-E325-11CE-BFC1-08002BE10318}001
Agora localize a entrada tipo REG_DWORD “Display1_DownScalingSupported” e altere o valor de 0 para 1.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E 968-E325-11CE-BFC1-08002BE10318}000
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E 968-E325-11CE-BFC1-08002BE10318}001
Agora localize a entrada tipo REG_DWORD “Display1_DownScalingSupported” e altere o valor de 0 para 1.
certifica lync communicator login user
Existe um certificado no micro validando a senha.
certutil -delstore -user My %username%@ulbra.br
este comando limpa o certificado
certutil -delstore -user My %username%@ulbra.br
este comando limpa o certificado
goto em comando script sh
#/bin/bash
iniciar() {
}
parar() {
}
case "$1" in "start") iniciar ;;
"stop") parar ;;
"restart") parar; iniciar ;;
*) echo "Use os parametros start, stop ou restart"
esac
iniciar() {
}
parar() {
}
case "$1" in "start") iniciar ;;
"stop") parar ;;
"restart") parar; iniciar ;;
*) echo "Use os parametros start, stop ou restart"
esac
consulta tivoli de espaço ocupado em disco
SELECT node_name,CAST(FLOAT(SUM(physical_mb)) / 1024 AS DEC(8,2))as "Space in GB",SUM(num_files)as"Number of files" FROM occupancy GROUP BY node_name
consulta tivoli quantas fitas por node
SELECT DISTINCT node_name,volume_name,stgpool_name FROM volumeusage WHERE NODE_NAME='APOLLO'
SELECT COUNT(*) FROM volumeusage WHERE NODE_NAME='APOLLO'
SELECT COUNT(*) FROM volumeusage WHERE NODE_NAME='APOLLO'
configura o tempo que expira no tivoli
define copygroup DB_ORACLE STANDARD ORACLE_DIARIO destination=BKP_POOL verexists=1 verdeleted=1 retextra=15 retonly=15
VALIDATE POLICYSET DB_ORACLE STANDARD
ACTIVATE POLICYSET DB_ORACLE STANDARD
VALIDATE POLICYSET DB_ORACLE STANDARD
ACTIVATE POLICYSET DB_ORACLE STANDARD
consulta do tivoli por data
select backup_date, filespace_name,type,hl_name,ll_name,state FROM backups WHERE node_name='LXDBOUL10' AND backup_date<=current_timestamp-30 days
compartilhar mais de 10 usuários xp
Remove the limit on TCP connection attempts
Windws XP SP2 introduces a few new twists to TCP/IP in order to babysit users and "reduce the threat" of worms spreading fast without control. In one such attempt, the devs seem to have limited the number of possible TCP connection attempts per second to 10 (from unlimited in SP1). This argumentative feature can possibly affect server and P2P programs that need to open many outbound connections at the same time.
Rant: The forward thinking of Microsoft developers here is that you can only infect 10 new systems per second via TCP/IP ?!?... If you also consider that each of those infected computers will infect 10 others at the same rate:
second 1: 1+10 computers
second 2: 10+10*10 computers (110 new ones)
second 3: 10+100*10 computers ( 1110 new ones)
second 4: 10+1000*10 computers (11110 new ones)
....
all the way to 10*60 + 10^60 computers in a single minute (that's a number with 60 digits, or it would far exceed Earth's population). Even if we consider that 90% of those computers are unreachable/protected, one would still reach ALL of them within a minute.
In other words, even though it is not going to stop worm spreading, it's going to delay it a few seconds, limit possible network congestion a bit, and limit the use of your PC to 10 connection attempts per second in the process ! I have no problem with the new default setting limiting outbound connection attempts. Still, users should have the option to easily disable or change this setting. I might be going out on a limb here, but ever since the introduction of Windows XP I can't help thinking that I dislike all the bult-in Windows "wisardry" in a sense that the system also limits user access. That irritating trend to ease the mental load on end users is somewhat insulting, considering that Windows is to make the more "intelligent" choice instead of the end user, as well as limit their access to tuning such settings...
End of rant.
With the new implementation, if a P2P or some other network program attempts to connect to 100 sites at once, it would only be able to connect to 10 per second, so it would take it 10 seconds to reach all 100. In addition, even though the setting was registry editable in XP SP1, it is now only possible to edit by changing it directly in the system file tcpip.sys. To make matters worse, that file is in use, so you also need to be in Safe mode in order to edit it.
You only need to worry about the number of connection attempts per second if you have noticed a slowdown in network programs requiring a number of connections opened at once. You can check if you're hitting this limit from the Event Viewer, under System - look for TCP/IP Warnings saying: "TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts". Keep in mind this is a cap only on incomplete outbound connect attempts per second, not total connections. Still, running servers and P2P programs can definitely be affected by this new limitation. Use the fix as you see fit.
To change or remove the limit, you can use the following program:
Event ID 4226 Patcher
- A patching program for removing or changing the
limit imposed on connection attempts in SP2. The patcher has the ability
to restore tcpip.sys back to the original... Still, you might want to
back up tcpip.sys, use it at your own risk. The author of this patch can
be reached @ http://www.lvllord.de/
Edit tcpip.sys manually to remove the TCP/IP socket creation limit
Another option, for the more adventurous is to modify your tcpip.sys file manually, using a hex editor. The following instructions refer to the final release of XP SP2, with a tcpip.sys file of exactly 359,040 bytes, CRC-32 is 8042A9FB, and MD5 is 9F4B36614A0FC234525BA224957DE55C. Even thouh there might be multiple tcpip.sys files in your system, make sure to work with the one in c:\windows\system32\drives\ directory.
To remove the tcpip.sys socket creation limit:
- Backup your original tcpip.sys file before editing please, this is somewhat important !
- In your hex editor, go to offset 4F322 hex (or 324386 decimal).
- Change 0a 00 00 00 to 00 00 0a 00
All done ! The above change does not require editing of the CRC in offset 130 hex (thanks for the clever solution Thomas Wolf Tompkins).
Notes:
If any of the data above does not match exactly (crc, file size, md5, or the data at offset 4F322) please double-check what you are doing, or abort completely.
The above information increases the RATE of opening outgoing connections. It has nothing to do with the limit of 10 connections to network shares on a Windows workstation PC for sharing files (a MS imposed limit to force you to upgrade to a server version of the OS). This 10 connections to network shares limit was introduced with NT4 workstation (SP3), and exists in Windows 2k workstation, and Windows XP home/pro/mc. It only applies to authenticated windows services, such as file and print sharing.
Windws XP SP2 introduces a few new twists to TCP/IP in order to babysit users and "reduce the threat" of worms spreading fast without control. In one such attempt, the devs seem to have limited the number of possible TCP connection attempts per second to 10 (from unlimited in SP1). This argumentative feature can possibly affect server and P2P programs that need to open many outbound connections at the same time.
Rant: The forward thinking of Microsoft developers here is that you can only infect 10 new systems per second via TCP/IP ?!?... If you also consider that each of those infected computers will infect 10 others at the same rate:
second 1: 1+10 computers
second 2: 10+10*10 computers (110 new ones)
second 3: 10+100*10 computers ( 1110 new ones)
second 4: 10+1000*10 computers (11110 new ones)
....
all the way to 10*60 + 10^60 computers in a single minute (that's a number with 60 digits, or it would far exceed Earth's population). Even if we consider that 90% of those computers are unreachable/protected, one would still reach ALL of them within a minute.
In other words, even though it is not going to stop worm spreading, it's going to delay it a few seconds, limit possible network congestion a bit, and limit the use of your PC to 10 connection attempts per second in the process ! I have no problem with the new default setting limiting outbound connection attempts. Still, users should have the option to easily disable or change this setting. I might be going out on a limb here, but ever since the introduction of Windows XP I can't help thinking that I dislike all the bult-in Windows "wisardry" in a sense that the system also limits user access. That irritating trend to ease the mental load on end users is somewhat insulting, considering that Windows is to make the more "intelligent" choice instead of the end user, as well as limit their access to tuning such settings...
End of rant.
With the new implementation, if a P2P or some other network program attempts to connect to 100 sites at once, it would only be able to connect to 10 per second, so it would take it 10 seconds to reach all 100. In addition, even though the setting was registry editable in XP SP1, it is now only possible to edit by changing it directly in the system file tcpip.sys. To make matters worse, that file is in use, so you also need to be in Safe mode in order to edit it.
You only need to worry about the number of connection attempts per second if you have noticed a slowdown in network programs requiring a number of connections opened at once. You can check if you're hitting this limit from the Event Viewer, under System - look for TCP/IP Warnings saying: "TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts". Keep in mind this is a cap only on incomplete outbound connect attempts per second, not total connections. Still, running servers and P2P programs can definitely be affected by this new limitation. Use the fix as you see fit.
Event ID 4226 Patcher
- A patching program for removing or changing the
limit imposed on connection attempts in SP2. The patcher has the ability
to restore tcpip.sys back to the original... Still, you might want to
back up tcpip.sys, use it at your own risk. The author of this patch can
be reached @ http://www.lvllord.de/Edit tcpip.sys manually to remove the TCP/IP socket creation limit
Another option, for the more adventurous is to modify your tcpip.sys file manually, using a hex editor. The following instructions refer to the final release of XP SP2, with a tcpip.sys file of exactly 359,040 bytes, CRC-32 is 8042A9FB, and MD5 is 9F4B36614A0FC234525BA224957DE55C. Even thouh there might be multiple tcpip.sys files in your system, make sure to work with the one in c:\windows\system32\drives\ directory.
To remove the tcpip.sys socket creation limit:
- Backup your original tcpip.sys file before editing please, this is somewhat important !
- In your hex editor, go to offset 4F322 hex (or 324386 decimal).
- Change 0a 00 00 00 to 00 00 0a 00
All done ! The above change does not require editing of the CRC in offset 130 hex (thanks for the clever solution Thomas Wolf Tompkins).
Notes:
If any of the data above does not match exactly (crc, file size, md5, or the data at offset 4F322) please double-check what you are doing, or abort completely.
The above information increases the RATE of opening outgoing connections. It has nothing to do with the limit of 10 connections to network shares on a Windows workstation PC for sharing files (a MS imposed limit to force you to upgrade to a server version of the OS). This 10 connections to network shares limit was introduced with NT4 workstation (SP3), and exists in Windows 2k workstation, and Windows XP home/pro/mc. It only applies to authenticated windows services, such as file and print sharing.
código das teclas
keycode 67 = F1
keycode 68 = F2
keycode 69 = F3
keycode 70 = F4
keycode 71 = F5
keycode 72 = F6
keycode 73 = F7
keycode 74 = F8
keycode 75 = F9
keycode 76 = F10
keycode 95 = F11
keycode 96 = F12
keycode 68 = F2
keycode 69 = F3
keycode 70 = F4
keycode 71 = F5
keycode 72 = F6
keycode 73 = F7
keycode 74 = F8
keycode 75 = F9
keycode 76 = F10
keycode 95 = F11
keycode 96 = F12
instalação hotspot/chillispot/freeradius/ad
apt-get install samba samba-common samba-common-bin winbind
apt-get install krb5
apt-get install krb5-auth-dialog libheimdal-kadm5-perl libkrb5-26-heimdal krb5-multidev krb5-user libkrb5-3 libkrb5-dbg libkrb5-dev libkrb5support0 krb5-admin-server krb5-kdc krb5-kdc-ldap krb5-pkinit libkrb53
apt-get install apache2
apt-get install libapache2-mod-auth-kerb libapache2-authenntlm-perl apache2-utils apache2.2-common apache2.2-bin
apt-get install ssl-cert
apt-get install freeradius freeradius-common freeradius-dbg freeradius-utils libfreeradius-dev libfreeradius2 freeradius-dialupadmin freeradius-iodbc freeradius-krb5 freeradius-ldap freeradius-mysql freeradius-postgresql
apt-get install xinit
apt-get install adjtimex
apt-get install krb5
apt-get install krb5-auth-dialog libheimdal-kadm5-perl libkrb5-26-heimdal krb5-multidev krb5-user libkrb5-3 libkrb5-dbg libkrb5-dev libkrb5support0 krb5-admin-server krb5-kdc krb5-kdc-ldap krb5-pkinit libkrb53
apt-get install apache2
apt-get install libapache2-mod-auth-kerb libapache2-authenntlm-perl apache2-utils apache2.2-common apache2.2-bin
apt-get install ssl-cert
apt-get install freeradius freeradius-common freeradius-dbg freeradius-utils libfreeradius-dev libfreeradius2 freeradius-dialupadmin freeradius-iodbc freeradius-krb5 freeradius-ldap freeradius-mysql freeradius-postgresql
apt-get install xinit
apt-get install adjtimex
limpar o swap squid
/etc/init.d/squid stop
rm -rf /var/log/squid/*
rm -rf /var/spool/squid/*
sleep 10
squid -z reconfigure
sleep 10
/etc/init.d/squid start
sleep 10
/etc/init.d/squid reload
rm -rf /var/log/squid/*
rm -rf /var/spool/squid/*
sleep 10
squid -z reconfigure
sleep 10
/etc/init.d/squid start
sleep 10
/etc/init.d/squid reload
redirecionar rota de ip
ip route add 193.233.7.98 via 193.233.7.254
*****ver essa rota
ip route get 193.233.7.98
*****ver essa rota
ip route get 193.233.7.98
redirecionamento de portas e ip
echo "1" > /proc/sys/net/ipv4/ip_forward
sysctl net.ipv4.ip_forward=1
iptables -t nat -A PREROUTING -p tcp --dport 1316 -j DNAT --to-destination 172.18.152.223:1316
iptables -t nat -A POSTROUTING -j MASQUERADE
iptables -t nat -A PREROUTING -p tcp -i eth1 --dport 1316 -j REDIRECT --to-destination 172.18.152.223:1316
sysctl net.ipv4.ip_forward=1
iptables -t nat -A PREROUTING -p tcp --dport 1316 -j DNAT --to-destination 172.18.152.223:1316
iptables -t nat -A POSTROUTING -j MASQUERADE
iptables -t nat -A PREROUTING -p tcp -i eth1 --dport 1316 -j REDIRECT --to-destination 172.18.152.223:1316
Redirecionar tráfego iptables
iptables -t nat -A PREROUTING -p tcp -i eth1 --dport 1316 -j REDIRECT --to-destination 172.18.152.223:1316
fixar endereco fisico na placa de rede
ifconfig eth2 hw ether 00:50:22:8d:37:82
ou no interfaces
auto eth0
iface eth0 inet dhcp
hwaddress ether 00:e0:7d:a5:9f:d1
ou no interfaces
auto eth0
iface eth0 inet dhcp
hwaddress ether 00:e0:7d:a5:9f:d1
ver ip externo sem interface grafica
wget -q http://www.omeuip.com/
IP_EXTERNO=`awk '/Your ip is/ {print $4}' index.html`
echo "Endereco IP externo: $IP_EXTERNO"
#rm index.html
IP_EXTERNO=`awk '/Your ip is/ {print $4}' index.html`
echo "Endereco IP externo: $IP_EXTERNO"
#rm index.html
correção sipe communicator pidgin
echo -e '#!/bin/sh\n\nNSS_SSL_CBC_RANDOM_IV=0 exec /usr/bin/pidgin\n' >/usr/local/bin/pidgin && chmod +x /usr/local/bin/pidgin
comandos com o dd monitoramento de copia e outros
1. Clonar disco e verificar andamento da cópia.
dd if=/dev/sda of=/dev/sdb bs=64k count=100; while :;do killall -USR1 dd;sleep 1;done
2. Descrobir o processo do dd
pgrep -l ‘^dd$’;
3. Monitorar o processo
kill -USR1 “id do processo”
watch df -h
4. Clonar disco para um diretório remoto usando ssh com compressão
dd if=/dev/sda | gzip -c | ssh root@ip ‘dd of=/mnt/backups/sda.dd’
5. Criar iso de disco, partição ou diretório
dd if=/etc of=/home/etc-bkp.iso
6. Formatar disco
dd if=/dev/zero of=/dev/sda
dd if=/dev/sda of=/dev/sdb bs=64k count=100; while :;do killall -USR1 dd;sleep 1;done
2. Descrobir o processo do dd
pgrep -l ‘^dd$’;
3. Monitorar o processo
kill -USR1 “id do processo”
watch df -h
4. Clonar disco para um diretório remoto usando ssh com compressão
dd if=/dev/sda | gzip -c | ssh root@ip ‘dd of=/mnt/backups/sda.dd’
5. Criar iso de disco, partição ou diretório
dd if=/etc of=/home/etc-bkp.iso
6. Formatar disco
dd if=/dev/zero of=/dev/sda
alterar o endereço físico da placa de rede mac address
# ifconfig eth0 down
# ifconfig eth0 hw ether 00:11:22:33:44:55
# ifconfig eth0 up
# ifconfig eth0 hw ether 00:11:22:33:44:55
# ifconfig eth0 up
Assinar:
Postagens (Atom)