• Posts

  • Joined

  • Last visited

Everything posted by arox

  1. "called by snmpcd (snmp formating)" As you and Werner say : the best solutions are often the simplest. The problem is to find what is really the simplest and to make the difference between simple and basic in a use case. (This is just a bit of general thinking (and nostalgy), as I have no idea about what you are working on). The **simple** network management protocol is surely basic but I never found it was simple and it has been a long time since I saw someone care about it. One more time, this is just general thinking, but I feel we use today a lot of complicated but no so powerful technologies in IT. Linux is a unix derivative, UNix has been designed by people who wanted a simple but powerful system after having worked on MULTix. I try to keep that in mind. But it is not always easy and cannot be achieve if we want our computers to also toast bread and do the laundry.
  2. In shell, pipes and awk are your bests friends : perhaps something like this : $ mkfifo /tmp/timefifo $ awk -W interactive -F: '{printf("cmd=%s s=%f\n", $1, $2*60+$3)}' <>/tmp/timefifo > /tmp/stats & $ /usr/bin/time -o /tmp/timefifo -f "%C:%E" ls -l $ /usr/bin/time -o /tmp/timefifo -f "%C:%E" ls $ /usr/bin/time -o /tmp/timefifo -f "%C:%E" who $ cat /tmp/stats cmd=ls -l s=0.700000 cmd=ls s=0.070000 cmd=who s=0.000000 $ killall awk N.B. : <> open the pipe in read/wite mode to prevent it to be closed when "time" send EOF.
  3. "time" is "built in" into the shell. In order to use the full version described by "man", you should first install the full version in /usr/bin/time : # apt-get install time. And call it with the full path. Also, when man fail to give doc because a package is missing, just google "man cmd".
  4. "Are there other things I can do aside from these I have done?" Lowering DRAM refresh rate was the most efficient powersaving trick. But I don't know if and how it can be done with modern kernel ?
  5. Hum ! Is address 6e:e4:fe:d4:82:6d a valid mac-address ? It seems to me that the first bit of first octet shouln't be 1 because it is reserved to multicast addresses. Sorry, my mistake, 6e is odd !!! Sorry, it is even so first bit 0. I go to bed ...
  6. There are a number of issues with the numerous versions of nfs, locking, architecture and export path on server with nfsV4 ... and I wouldn't trust error messages. For example "protocol not supported" can be emitted because of the share path semantic : From : mount.nfs: Protocol not supported This error occurs when you include the export root in the path of the NFS source. For example: # mount SERVER:/srv/nfs4/media /mnt mount.nfs4: Protocol not supported Use the relative path instead: # mount SERVER:/media /mnt I have had some troubles in the past with export path and nfsV4 and it works at present although my configuration is not supposed to be correct ?!?
  7. "f you want control and your apps are available, try OpenBSD, very hands on, secure *nix ..." I use a Gentoo system to concentrate and serve all network and security functions. This one would be a good candidate for OpenBSD. But I never used an OpenBSD system. Not really a problem (I have used dozen of *nix systems and BSD was the first one) but I do not know on which SBC, light platform or appliance it could be easily installed (and reliable) ?
  8. systemd-shim is provided by debian. I do not know what may fail without it. (It is said to translate systemd helpers and anyway I have no use for automatic service start and stop on a personally administered system). "dhcp, with the router reserving ip addr for your client mac addr" Well, I am not sure there exists a "good solution". Anyway, I prefer editing a central repository than having (bugged) auto-configuration systems. Auto configuration is mandatory in some cases and a pain in the neck as soon as you have a problem and are not sure where it lies. That is why I removed systemd one more time (I kept it 3 months which is a record-breaking event for me). In this precise case, it is because the network interface needs sometimes a reset at boot (which stall the boot process), that the problem is known to happen in my case with D-link switches - and not handled of course ... I simply cannot patch systemd to resolve all mishappenings by editing meta-configuration files everywhere and praying it will convince systemd to resolve the problems disregarded by mainstream maintainers.
  9. For info, I managed to get rid of systemd on my raspbian desktop. I had to first install dbus-x11 because the dependencies would force half of packages removal. Then installation of sysvinit-core do the trick and trigger install of libnih-dbus1, systemd-shim, libcgmanager0, libnih1, cgmanager and "pinned out" systemd. You probably need to install : ntp and ntpdate and of-course I use a totally static network configuration. (No avahi, no networmanager, no dhcpcd ...) Also, I needed to modify /etc/X11/Xwrapper.config because of DRM driver needing root uid of X server. Of course, I do that sort of things only after reaching a stable configuration that I can maintain without support and with a good system backup !
  10. You didn't say if pihole works or not. I do not think ifconfig is able to report complex configurations correctly. (That may or may not work). Anyway it is recommended in pihole tutorials to setup a static IP address. For example edit : /etc/dhcpcd.conf. # Example static IP configuration: interface eth0 static ip_address= #static ip6_address=fd51:42f8:caae:d92e::ff/64 static routers= #adresse IP du modem/routeur #static domain_name_servers= fd51:42f8:caae:d92e::1 Note that you need to be careful to specify the correct bitmask : means a 24 bit netmask although your router may think otherwise.
  11. With 32 GB emmc ?!? That is an option that generally costs the price of a RPI.
  12. Many seems to think that theirs has to be very long and powerful (if you understand what I mean). In fact, a well designed enclosure can assume this function. And in any case the quality of the thermal interface is more important than anything else.
  13. Manufacturers will always add all hardware features that does not cost a lot : i.e. crappy cheap wifi and so on, because they do not bother to provide good drivers. In the other hand, RAM is always priced a lot and thermal design bad. If I want a SBC for specific use case like computing (and not a X86 server), I want it to be passively cooled and energy efficient. Storage is also a choice : either emmc, either a good bus design for drives. I simply cannot find a SBC for a use case because they are all designed for "general purpose" like a RPI or expensive with no guarantee of software support.
  14. Stupid us ! For me configuring is like programing. We need to check live parameters to debug configuration or design mistakes. I wish I would know how to debug efficiently some declarative languages ...
  15. cat /sys/devices/platform/sunxi-i2c.0/i2c-0/0-0034/axp20-supplyer.28/power_supply/ac/voltage_now is not present om my Banana Pi. Well my kernel is outdated. You can find the correct path in armbianmonitor script.
  16. Check you have the same netmask on router, bridge and dhcp config. Check router arp tables and messages to see if it receive requests. Check if interfaces are really added to the bridge with brctl and that some nasty software has not added addresses to wlan0 and eth0 with ifconfig.
  17. Perhaps you should try another PSU or check your cables : your voltage drop low at 960 MHz and you got SATA errors and reset. Try : cat /sys/devices/platform/sunxi-i2c.0/i2c-0/0-0034/axp20-supplyer.28/power_supply/ac/voltage_now while transferring files.
  18. I would like DT overlay could handle that sort of thing. (I may suggest here something completely stupid because I know nothing about DT). Using an overkilled dynamic system configuration system like udev to make a static configuration is somewhere strange ...
  19. The method "filtering by devpath" I have indicated before is targeted at providing a solution in that case. The match is done for a type of (identical) devices (same idVendor/idProduct) and the device name chosen according to the index of USB port.
  20. Good question ! The name depends not only on boot but also change if you plug / unplug devices ... I have the same problem when I try to work with 2 micro-controllers at the same time. This can certainly be done with an "udev rule". There is some response here : In section : filtering by "devpath" : SUBSYSTEM=="tty", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="7523", ATTRS{devpath}=="1.2", SYMLINK+="ttyUSB-arduino1" SUBSYSTEM=="tty", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="7523", ATTRS{devpath}=="1.5", SYMLINK+="ttyUSB-arduino2" The solution will depend on usage and usb hub configuration. And writing and debugging udev rules is not easy.
  21. What happens if you just create it ? (sudo touch /var/log/wtmp)
  22. "it should have plenty of power to run the board and hdd" This is a recurrent question on this forum. But the voltage available to the board always depends on the source voltage and also on the cable(s), contacts of connectors and internal circuits resistance, protection diodes and fuses, (and of the PSU mileage which is difficult to evaluate) ... When the board needs too much current, the total resistance can make the input voltage drop below the minimum needed for a time too short to see on a multimeter but that may cause any sort of hardware failure. If you never changed anything and never moves cables, forget that : but if you replugged the power connector of the BPI M1, be sure to use the one next to the SCSI connector and check that half the strands of your cable are not cut. (As it happened to me a lot of time). "PC power source" : A PC Power Supply has plenty of power but not a USB port which has current limitation and protection circuitry. I do not think your card could boot if the SBC and the disk were powered thru a single USB port. As tparys said, you should also check that fsck is requested at boot (kernel parameter "" in "modern" linux - but yours - as mine - is perhaps a little less modern), because you always will face a power outage some time that the journalization of the fs cannot handle.
  23. BTW A possible cause of repeated fs corruption is the power supply. (Or power cables).
  24. Hum ! A bit worrying that your second fsck complained. I do not understand why you couldn't unmount the fs or /dev/sda1 was not present and appeared the second time ? Did you run fsck with the fs mounted ro ? The fs is probably repaired now but you should check your logs and have an up-to-date backup during some times. There are commands to check disk errors recorded by firmware (but not controller or cables errors). Anyway I experienced your problems a lot of times and still use the board and cards without problem. Yes, BPI M1 with armbian was and always is a good solution. That is why I still use it although it is completely out-of-date. But I got the same sort of fs corruption case (triggered by usb bugs ?) with raspbian on RPI4.