Solved how to run command for specified online normal user with root in freebsd14.2 ?

Next step is to create a regular user account on that machine for yourself.

Then add that account to the wheel group.

I'm assuming that this is a personal machine/VM, not a work machine/VM.

Your initial post actually states that you have just two users on your new system, gdman and root. So, it's quite logical to assume that you are gdman on the system. And in this case, it's quite baffling that you don't have the password for gdman. If you locked yourself out of a brand-new system, just reinstall it. And while doing the reinstall, add yourself to the wheel group!
DEar astyle :
thanks for your reply. ok. i show your next envorionment in below .
1. a,b,c,d,e, root . 6 user in one machine . i don't know a,b,c,d user password. only e and root password i known. and e was wheel group .
2. a,b,c,d,e normal user using gnome GUI desktop.
3. how to run a command (chrome , thunderbird, transmission-daemon ) for "a" user, and show GUI at his desktop from root ?

i know you told me, first login e and su root , then what is the next ? thanks.
 
Once you are root, it's probably not impossible to run su a, and then follow instructions in post #2.

But I would not bet on it, especially if you don't know the password for user a.

On the other hand, if you log into that machine as user e and then SSH in from the side as user e, then it would make sense.

There's kind of a reason why processes from different users cannot easily communicate and interfere with each other - the very design of UNIX is to prevent that. I've had that happen to me on Windows, and I absolutely hated that. But that's another story.

The su(1) manpage (which I recommend that you read) is a pretty short one. Just a heads up: Reading a manpage is one thing. Understanding it and applying it to yourself to solve a problem - that's a very different thing.

I realize that English is not your native language, fff2024g , so it may be difficult to properly express and/or translate some pretty important security concepts in a way that makes sense and is correct in both languages.
 
xroach -display :0 , but nothing happened .

The traditional xroach program does the following: You start it, and it shows a few cockroaches on the screen. Very quickly, they run around the screen, and within a fraction of a second they hide behind windows. There, they remain invisible, until you move or close a window and expose them. Then the exposed ones quickly run around, and find another window to hide under.

If you're not paying close attention, you might completely miss what xroach actually does. If you are doing screen-intensive work, I would recommend watching its CPU usage. And if you have a giant window that covers the whole screen, and has other windows in front of it, it takes the whole fun out of xroach, as the bugs will always remain hidden.

By default, the number of cockroaches is quite small, dozens. But we have to consider that the original xroach program was written about 40 years ago, when CPUs were much slower. For the best effect, use the command-line option to have many many roaches, many hundreds. Also, in some versions of xroach (or depending on an option), it will allow roaches to be squished by clicking on them with a mouse (which is quite difficult, as they run fast). That kills the roach, leaving disgusting looking dirt on the screen.

There also used to be a program called xsnoopy that worked similarly: At random times, a snoopy (the cartoon dog) would walk around the screen. Again, its main purpose was to annoy coworkers.
 
1740119875674.png
 
The traditional xroach program does the following: You start it, and it shows a few cockroaches on the screen. Very quickly, they run around the screen, and within a fraction of a second they hide behind windows. There, they remain invisible, until you move or close a window and expose them. Then the exposed ones quickly run around, and find another window to hide under.

If you're not paying close attention, you might completely miss what xroach actually does. If you are doing screen-intensive work, I would recommend watching its CPU usage. And if you have a giant window that covers the whole screen, and has other windows in front of it, it takes the whole fun out of xroach, as the bugs will always remain hidden.

By default, the number of cockroaches is quite small, dozens. But we have to consider that the original xroach program was written about 40 years ago, when CPUs were much slower. For the best effect, use the command-line option to have many many roaches, many hundreds. Also, in some versions of xroach (or depending on an option), it will allow roaches to be squished by clicking on them with a mouse (which is quite difficult, as they run fast). That kills the roach, leaving disgusting looking dirt on the screen.

There also used to be a program called xsnoopy that worked similarly: At random times, a snoopy (the cartoon dog) would walk around the screen. Again, its main purpose was to annoy coworkers.
Dear ralphbsz :
whatever i do , nothing happened .. now i have gnome GUI desktop. then open terminal . input xroach command . nothing get it. thanks.
 
Once you are root, it's probably not impossible to run su a, and then follow instructions in post #2.

But I would not bet on it, especially if you don't know the password for user a.

On the other hand, if you log into that machine as user e and then SSH in from the side as user e, then it would make sense.

There's kind of a reason why processes from different users cannot easily communicate and interfere with each other - the very design of UNIX is to prevent that. I've had that happen to me on Windows, and I absolutely hated that. But that's another story.

The su(1) manpage (which I recommend that you read) is a pretty short one. Just a heads up: Reading a manpage is one thing. Understanding it and applying it to yourself to solve a problem - that's a very different thing.

I realize that English is not your native language, fff2024g , so it may be difficult to properly express and/or translate some pretty important security concepts in a way that makes sense and is correct in both languages.
DEar astyle :
thanks for your time to help me .
1. machine was freebsd14.2 with gnome GUI.
2. a,b,c ,normal user, a was wheel user.
3. i have got a user password.
4. a user login directly this machine with gnome GUI.
5. i have ssh login this machine from remote with a user in shell.
6. now ,do i still need fellowing the Post#2 step to run command and show it in a user Gnome GUI desktop ?
thanks.
 
Dear ralphbsz :
whatever i do , nothing happened .. now i have gnome GUI desktop. then open terminal . input xroach command . nothing get it. thanks.
It is possible that Gnome has done something to break it. Try running X alone without a window manager, or with a really simple one like FVWM or TWM.
 
Dear fff2024g, we are now up to post #34 on this thread.

I provided a solution to your problem at post #2.

You are clutching at straws as they fly by, but grasping none.

I suggest you try the solution I gave you. But don't use chromium, it's too complex. If xroach does nothing, try xclock. Just login as root and do it.

If it works, we can discuss how to avoid the root login.

If it does not work, please tell us exactly what you did, and exactly what the result was.

You can format your response by using the XenForo BB Codes. The CODE directive is useful for showing commands and error messages.
 
Dear fff2024g, we are now up to post #34 on this thread.

I provided a solution to your problem at post #2.

You are clutching at straws as they fly by, but grasping none.

I suggest you try the solution I gave you. But don't use chromium, it's too complex. If xroach does nothing, try xclock. Just login as root and do it.

If it works, we can discuss how to avoid the root login.

If it does not work, please tell us exactly what you did, and exactly what the result was.

You can format your response by using the XenForo BB Codes. The CODE directive is useful for showing commands and error messages.
Dear gpw928:
thanks for your more time to solve the same question. very thanks. i will close this topic. thanks.
 
Back
Top