Interesting: some PowerShell scripts that pipe a user and password through cmdkey.exe /generic:TERMSRV/$Computer /user:$User /pass:$Pass
- [WayBack] Remote Desktop Auto Login Powershell Script · GitHub
- [WayBack] mstsc auto login command line
–jeroen
Archive for the ‘Linux’ Category
Remote Desktop Auto Login Powershell Script · GitHub
Posted by jpluimers on 2020/05/29
Posted in *nix, Development, Linux, Power User, Software Development | Leave a Comment »
Best android apps for zabbix – AndroidMeta
Posted by jpluimers on 2020/05/28
If I land a project using Zabbix again, one of the things I need to look into is [WayBack] Best android apps for zabbix – AndroidMeta.
- [WayBack] Android Zabbix Triggers Widget | Blog-IT-Technik
- [WayBack] GitHub – inovex/zax: Zabbix frontend for Android
- [WayBack] Reddit – Android apps for zabbix 3 : zabbix
- [WayBack] [Zabbkit] Push notifications on your smartphone – ZABBIX Forums
–jeroen
Share this:
Posted in *nix, Android, Android Devices, Development, Linux, Mobile Development, Monitoring, Power User, Zabbix | Leave a Comment »
Raspberry Pi 1B OpenSuSE Tumbleweed zypper upgrade problem · GitHub
Posted by jpluimers on 2020/05/25
It looks like OpenSuSE has stopped supporting Raspberry Pi 1, so the best likely is to recycle it into a Pi-Hole as basically it’s been dead since mid 2017: [WayBack] Raspberry Pi 1B OpenSuSE Tumbleweed zypper upgrade problem · GitHub.
Build status for armv6l support: [WayBack] Project openSUSE:Factory:ARM Status Monitor – openSUSE Build Service
–jeroen
Share this:
Posted in *nix, *nix-tools, Debian, Development, Hardware Development, History, Linux, openSuSE, Power User, Raspberry Pi, Raspbian, SuSE Linux, Tumbleweed | Leave a Comment »
ipmi – Linux: Why does Single User mode work on Serial Console but not on the attached Keyboard/Video/Monitor? – Server Fault
Posted by jpluimers on 2020/05/19
From [WayBack] ipmi – Linux: Why does Single User mode work on Serial Console but not on the attached Keyboard/Video/Monitor? – Server Fault (slightly edited; thanks Patrick!):
Becauseinithas not spawned off multiple TTYs yet (getty,mgetty, etc), so you only have the primary TTY. The primary TTY is the lastconsole=parameter on the kernel command line. All the console parameters get the output, but only the last one will be able to act as input.
–jeroen
Share this:
Posted in *nix, Debian, Linux, openSuSE, Power User, RedHat, SuSE Linux, Tumbleweed | Leave a Comment »
Show openSUSE:Factory / bootchart – openSUSE Build Service
Posted by jpluimers on 2020/05/15
On my research list: [WayBack] Show openSUSE:Factory / bootchart – openSUSE Build Service.
I bumped here when researching on how to list services: [WayBack] init.d – Command to list services that start on startup? – Ask Ubuntu
It seems few people use it on opensuse, but it is interesting for analysing the boot process nonetheless.
I already found out this is in fact bootchart2: [WayBack] GitHub – xrmx/bootchart: merge of bootchart-collector and pybootchartgui
Some links that should help me further are these:
- [WayBack] Sistemos paleidimo trukmės analizė openSUSE linux operacinės sistemos naujienų, pagalbos svetainė.
- Google translated: [WayBack] System runtime analysis for openSUSE linux operating system
- [Google Cache/WayBack] http://download.vikis.lt/lietukas/Dokumentacija/openSUSE%20patyrusiems.odt
From the last link, this translation:
A. systemd-analyze
You will see the total computer startup time after:
systemd-analyze
A complete list of how much each individual service has taken is when you complete:
systemd-analyze blame
You will see the most problematic processes after you complete:
systemd-analyze critical-chain
You can create a picture:
systemd-analyze plot> /tmp/systemd-analyze.svg
Suitable for: openSUSE 11.4, 12.x, 13.1, Leap 42.x
Not suitable: openSUSE 13.2
B. bootchart
First, install the bootchart package (bootchart 2 version of the program). If you are using openSUSE Leap 42.x or later, enable bootchart2 (and optional bootchart2-done) service:
systemctl enable bootchart2
systemctl enable bootchart2-done
If you are using openSUSE version 13.1 or earlier, go to YaST → (System) → Startup and enter kernel startup parameters:
initcall_debug printk.time = y quiet init = / sbin / bootchartd rdinitrd = / sbin / bootchartd
The next time you start your computer, the /var/log/bootchart.png image will be created to help you further optimize your system startup. For example, if you do not need an AppArmor who cares about security, you can disable the boot.apparmor service through the YaST Service Configuration Module.
Suitable for: openSUSE 11.4, 12.x, 13.1, 13.2, Leap 42.x
–jeroen
Share this:
Posted in *nix, *nix-tools, Linux, openSuSE, Power User, SuSE Linux, Tumbleweed | Leave a Comment »
