Interesting thought [WayBack] In windows, can I redirect stdout to a (named) pipe in command line? – Super User.
The only problem seems to be a good way of creating/removing those pipes.
–jeroen
Archive for the ‘Scripting’ Category
In windows, can I redirect stdout to a (named) pipe in command line? – Super User
Posted by jpluimers on 2019/01/14
Posted in Batch-Files, Development, Power User, Scripting, Software Development, Windows | Leave a Comment »
List of Shell GUIDs for various Windows versions for use in shortcuts and batch files
Posted by jpluimers on 2019/01/09
In my search for starting the Windows Credential Manager from the console, I found [WayBack] Credential Manager Shortcut – Create – Windows 7 Help Forums explaining:
%windir%\explorer.exe shell:::{1206F5F1-0569-412C-8FEC-3204630DFB70}
This reminded me of From batch file or shortcut: start Windows Update (via: Windows 7 Help Forums) and batch-file trick: Starting Windows Explorer and selecting a file (“explorer” commandline parameters “/n” “/e” “/select” “/root” “/start” site:microsoft.com).
The odd thing is that some of the GUID shortcuts works fine using the shell::: syntax, but fail with the /e:: syntax, for instance Windows Update until Windows 8.1:
%windir%\explorer.exe shell:::{36eef7db-88ad-4e81-ad49-0e313f0c35f8}
%windir%\explorer.exe /e,::{36eef7db-88ad-4e81-ad49-0e313f0c35f8}
One day I’ll create a table of permutations for various Windows versions and execute options.
For now these links need to suffice:
- [WayBack] CLSID Key (GUID) Shortcuts List for Windows 10 Windows 10 Customization Tutorials
- [WayBack] CLSID Key (GUID) Shortcuts List for Windows 8
- [WayBack] CLSID Key List for Windows 7 – Windows 7 Help Forums
- [WayBack] SOLVED Creating 23 desktop icons similar to Windows 7 Start menu to – Microsoft Community
- [Archive.is] Understanding Windows 7’s ‘GodMode’ – CNET
- [Archive.is] Windows 7 has lots of ‘GodModes’ (exclusive) – CNET
–jeroen
Share this:
Posted in Batch-Files, Development, Power User, Scripting, Software Development, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows 9 | 1 Comment »
Easy Running of Scripts at Boot and Shutdown – SUSE Blog | SUSE Communities
Posted by jpluimers on 2019/01/01
Cool:
- Easy Running of Scripts at Boot and Shutdown – SUSE Blog | SUSE Communities [WayBack]
- opensuse – How to run my script after SuSE finished booting up? – Unix & Linux Stack Exchange [WayBack]
- [WayBack-only] systemd and using the after.local script in openSUSE 12.1/12.2/12.3 – Blogs – openSUSE Forums
- Debugging an /etc/init.d service when it fails silently [WayBack]
- shell – debugging /etc/init.d startup scripts in Ubuntu – Stack Overflow [WayBack]
- Debugging Bash scripts [WayBack]
/etc/init.d/after.local
–jeroen
Share this:
Posted in *nix, *nix-tools, bash, Development, Linux, openSuSE, Power User, Scripting, Software Development, SuSE Linux, Tumbleweed | Leave a Comment »
Python 2.7 Countdown: a year from now it is unsupported
Posted by jpluimers on 2019/01/01
Besides wishing you a happy new year, also a reminder: [WayBack] Python 2.7 Countdown Python 2.7 will retire on januari 1, 2020. Learn more and see the countdown here.
This is indeed a breaking change for Python users, similar as from Perl 4 to Perl 5, and PHP 4 to PHP 5.
It shows two things:
- how extremely hard it is to evolve a language without breaking things
- how long it takes for the community at large to digest breaking changes
And indeed porting of complex systems is hard [WayBack] WIP: Port calibre to python 3 by flaviut · Pull Request #870 · kovidgoyal/calibre · GitHub but doable [WayBack] Bug #1714107 “Python 2 is retiring” : Bugs : calibre.
Via: [WayBack1/WayBack2] Python 3 improves in some ways over Python 2, but also makes a bunch of changes that are breaking, but cosmetic (i.e. renaming methods and functions, or… – Kristian Köhntopp – Google+ (with some interesting comments, but also a rant-sequence of someone who would better use that energy to improve Python than to bash it).
–jeroen
Share this:
Posted in Development, Python, Scripting, Software Development | Leave a Comment »
eventviewer – filtering on service stop/start events
Posted by jpluimers on 2018/12/27
Based on eventviewer – View Shutdown Event Tracker logs under Windows Server 2008 R2 – Server Fault « The Wiert Corner – irregular stream of stuff, I’ve made similar filters for service stop/start events.
Works on translated systems:
PowerShell
Get-EventLog System | Where-Object {$_.EventID -eq "7036"} | ft Machinename, TimeWritten, UserName, EventID, Message -AutoSize -Wrap
Or on one line:
Get-EventLog System ^| Where-Object {$_.EventID -in "6005","6006","7000","7009","7036","7040","7042","7043","7045"} ^| ft Machinename, TimeWritten, UserName, EventID, Message -AutoSize -Wrap
Note the -In operator was introduced in PowerShell 3: [WayBack]
Source: PowerShell v3 – New -in Operator | Jonathan Medd’s Blog
I’ve adapted the custom view to include all these event IDs above (note some links have disappeared moving my notes to a blog post):
- [WayBack] 6005: The Event log service was started (indication for system startup).
- [WayBack] 6006: The Event log service was stopped (indication for system shutdown).
- [WayBack] 7000: The <servicename> service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion. - [WayBack] 7009: A timeout was reached (30000 milliseconds) while waiting for the <servicename> service to connect.
- [WayBack] 7036:
- The <servicename> service entered the stopped state.
- The <servicename> service entered the running state.
- [WayBack] 7040: The start type of the <servicename> service was changed from demand start to auto start.
- [WayBack] 7042: The <servicename> service was successfully sent a stop control.
- [WayBack] 7043: The <servicename> service did not shut down properly after receiving a preshutdown control.
- [WayBack] 7045: A service was installed in the system.
Other event IDs that might be relevant via [WayBack] Windows Server restart / shutdown history – Server Fault:
- [WayBack] 6008: “The previous system shutdown was unexpected.” Records that the system started after it was not shut down properly.
- [WayBack] 6009: Indicates the Windows product name, version, build number, service pack number, and operating system type detected at boot time.
- [WayBack] 6013: Displays the uptime of the computer. There is no TechNet page for this id.
- [WayBack] 1074: “The process X has initiated the restart / shutdown of computer on behalf of user Y for the following reason: Z.” Indicates that an application or a user initiated a restart or shutdown.
- [WayBack] 1076: “The reason supplied by user X for the last unexpected shutdown of this computer is: Y.” Records when the first user with shutdown privileges logs on to the computer after an unexpected restart or shutdown and supplies a reason for the occurrence.
- [WayBack] 41 (source: Microsoft-Windows-Kernel-Power)
- [WayBack] 1001: (source: BugCheck).
- [WayBack] 12, which is typically the first eventid to be logged after a reboot/reset etc and shows the actual “system start time”, i.e.: “The operating system started at system time 2017-09-19T02:46:06.582794900Z.”
A more complete list of Windows Kernel related Event IDs is at [WayBack] rootkit.com/NETEVENT.H at master · bowlofstew/rootkit.com.
Steps for the custom view:
Open Event Viewer then
- Right click Custom Views
- Click Create Custom View
- Under the Filter tab
- Keep Logged as Any time
- Select all the Event level types (Critical, Warning, etc.)
- Choose by source = Service Control Manager, Service Control Manager Performance Diagnostic Provider
- Optionally; For Event ID under the Includes/Excludes Event IDs section enter 6005,6006,7000,7009,7036,7040,7042,7043,7045 for the Event ID
- Click Ok
- Enter a name like Shutdown Events and any description then
- Click Ok again to complete the custom event log.
Your new custom view should show up in the list of custom views with the correct filter applied.
–jeroen
Share this:
Posted in CommandLine, Development, Power User, PowerShell, PowerShell, Scripting, Software Development, Windows | Leave a Comment »
