Sometimes you want to see exactly what a computer or application is trying to communicate with. Obviously you can take full a network packet capture and filter the results and correlate the behavior with the DNS traffic, but sometimes it is easier to watch these results live as they happen. One quick way to do this is use Wireshark, however not the full client but the command line version tshark. Tshark allows you to filter on specific facets of DNS giving you a cleaner output especially when you are only interested in domains that an application is talking to.
On installing Raspotify on a new build of Ubuntu 19.10 for Raspberry Pi I saw the following error: Raspotify installer only runs on a Raspberry Pi Not too much information there. Going through the manual install procedure you end up something more meaningful: N: Skipping acquire of configured file ‘main/binary-arm64/Packages’ as repository ‘https://dtcooper.github.io/raspotify raspotify InRelease’ doesn’t support architecture ‘arm64’ So unpacking that a bit it seems that in switching to using Ubuntu Server from Raspbian on my Linux Spotify connect Raspberry Pi’s the architecture is ARM64 (ARMv8) rather than using armhf.
Since Ubuntu 17.10 Artful, ifupdown has been replaced with Netplan. After each session trying to remember how to configure Netplan I seem to forget the locations and syntax. So this is for my aging memory. The configuration files for Netplan live in: /etc/netplan/ The default install of Ubuntu 18.04 leaves the following file: /etc/netplan/50-cloud-init.yaml As you can see the config file is in yaml. Unless specified manually the default install will give a simple file using DHCP.
Configuration files can be long and complex and it is hard to see which values have been set. There are numerous ways to do this however, grep with -v (–invert-match) is a quick way to achieve this. The following example removes all the comments from an elasticsearch configuration file: [email protected]:~$ sudo grep -v ‘#’ /etc/elasticsearch/elasticsearch.yml Which returns: cluster.name: es node.name: es01 network.host: 10.1.10.187 discovery.zen.ping.unicast.hosts: ["10.1.10.187", "10.1.10.124"] discovery.zen.minimum_master_nodes: 2 Five lines where it is easy to see what has been configured.
As of the 25/06/12 you need to use the bloody release and will also need to have a floppy drive attached. You can add the floppy drive through the VMware gui or add the following to your vmx file: floppy0.fileType = "file" floppy0.fileName = "path_to_/floppy_image/Omni.flp" floppy0.clientDevice = "FALSE" floppy0.startConnected = "FALSE" If you want to create a virtual floppy image then use the following on Os X: touch path_to_/floppy_image/Omni.flp I’m not sure you need to point to a real image, however if you are using the Fusion gui, it requires you to have one.
Use the following from a terminal to get the file size in bytes: wc -c ~/screenlog.0 Which in this case will output: 76974 /Users/edward/screenlog.0 Showing my screenlog.0 is 76974 bytes.
How about: Multi-queue support for VMXNET3 drivers. New support for VMXNET3 drivers provides the ability to scale throughput in a VMware vSphere 5 environment by assigning multiple cores to the Vyatta virtual machine. Sounds good to me.
Sometimes you need to use the operating system file manager rather than a terminal so a quick way of opening it can be seen below. For the Windows command line: explorer . The OS X terminal: open . The Ubuntu console: nautilus . This will work for parent folders .. as well as current directory. Note, in case you are interested to do the same in Haiku OS just use the OS X version.
You should use something like logrotate to manage you log files however sometimes you are not interested in the log content and just want to clear them. Especially if you have multi GB files due to excessive errors. In this situation use: > /var/log/logfile-name This will clear the file but not remove it. It is possible that a process has locked the file, in which case track it down with:
If you get the following error when generating a pacman keychain master key: pacman-key –init gpg: Generating pacman keychain master key… Not enough random bytes available. Please do some other work to give the OS a chance to collect more entropy! (Need 288 more bytes) It can be quite tricky to introduce entropy into this low powered headless system. I tried various methods all of which failed. You can monitor the available system entropy here: