Tag Info

New answers tagged

-1

user@host:~$ cd .. user@host:/home$ cd .. user@host:/$ echo " " | sudo tee txt.txt user@host:/$


2

Above and beyond the question of whether it's a good idea (it opens up the potential for a non-root user to fill up the root filesystem, causing havoc), you could accomplish this in several different ways: chmod a+w / -- to give "other" write permission chgrp somegroup /; chmod g+w /; usermod -G somegroup user -- to change the group ownership of / to a ...


2

The problem is not occurring because of the UID of the user. 500 is just fine as a UID, and that UID doesn't make it a 'non-login' user except in the eyes of the default settings of some few display managers. The error message No protocol specified sounds like an application-specific error message, and an unhelpful one at that, but I am going to guess that ...


0

More playing around with the alternate syntax, as well as another deep dive into the man page led me to the -s option. Hallelujah! It runs as a startup service! /sbin/runuser -s /bin/sh - nobody -c '/etc/ircd/bin/ircd -configfile /etc/ircd/ircd.conf -logfile /var/log/ircd/ircd.log' Only thing I'm worried about: If I'm now forcing nobody to be run with ...


0

Here is the wiki for configuring polkit rules for udisks/udisks2 in order to mount partitions by non-root (e.g. users) group. Save the code below to /etc/polkit-1/rules.d/50-udisks.rules polkit.addRule(function(action, subject) { var YES = polkit.Result.YES; var permission = { // only required for udisks1: ...



Top 50 recent answers are included