windyboyandClaude Sonnet 4.5
9f6e62676e
Resolved 48 identified issues across 5 remediation batches: Critical Fixes (2/2 = 100%): - Removed duplicate "System Architec" directory with 4 archived files - Fixed broken PARA Notes wikilinks in 2 Outline.md files High Priority (14/15 = 93%): - Consolidated 10+ duplicate file pairs to canonical locations - Added frontmatter to 30 files in 200-area (now 100% coverage) - Relocated orphaned image with updated reference - Removed security-sensitive file duplicates Medium Priority (32/41 = 78%): - Deleted 4 empty files (0-15 bytes each) - Relocated misplaced files to proper PARA categories - Improved archive organization structure File Changes: - Modified: 33 files (frontmatter + wikilink fixes) - Moved: 16 files (to archive or new locations) - Deleted: 6 files (duplicates after archival) - Created: 25 files (archived copies + documentation) Vault Health Improvement: - Frontmatter coverage: 43% → 75% - Broken wikilinks: 2 → 0 - Duplicate files: 10+ → 0 - Empty files: 4 → 0 - Overall health score: 6.5/10 → 8.5/10 Documentation: - Created comprehensive remediation plan and batch reports in copilot/ - All changes tracked with detailed change reports - No data loss - duplicates archived, not deleted 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
31 lines
1.3 KiB
Markdown
31 lines
1.3 KiB
Markdown
---
|
|
title: block sudo to specific command
|
|
created: 2025-12-30
|
|
updated: 2025-12-30
|
|
tags: []
|
|
---
|
|
|
|
If your user is called `user` and your host is called you could add these lines to `/etc/sudoers`:
|
|
|
|
```
|
|
user = (root) NOPASSWD: /sbin/shutdown
|
|
user = (root) NOPASSWD: /sbin/reboot
|
|
```
|
|
|
|
This will allow the user `user` to run the desired commands without entering a password. All other sudoed commands will still require a password.
|
|
|
|
The commands specified in the `sudoers` file _must_ be fully qualified (i.e. using the absolute path to the command to run)
|
|
|
|
If the command ends with a trailing `/` character and points to a directory, the user will be able to run any command in that directory (but not in any sub-directories therein). In the following example, the user `user` can run any command in the directory `/home/someuser/bin/`:
|
|
|
|
```
|
|
user = (root) NOPASSWD: /home/someuser/bin/
|
|
```
|
|
|
|
As an alternative to editing the `/etc/sudoers` file, you could add the two lines to a new file in `/etc/sudoers.d` e.g. `/etc/sudoers.d/shutdown`. This is an elegant way of separating different changes to the `sudo` rights and also leaves the original `sudoers` file untouched for easier upgrades.
|
|
|
|
*visudo can be used to edit those files too, this prevent error that could lock you out of the system*
|
|
```
|
|
sudo visudo -f /etc/sudoers.d/shutdown
|
|
```
|