On Saturday 19 December 2020 03:32:07 Gene Heskett wrote:
Now I need some cross permissions help.
I have added two dcop commands to my backup.sh that are: /opt/trinity/bin/dcop kmail KMailIface pauseBackgroundJobs and: /opt/trinity/bin/dcop kmail KMailIface resumeBackgroundJobs
Specified as Cmdholdit and Cmdresume
and called as $Comdholdit and $Cmdresume
But this script run as amanada, who is part of the backup group and this error or generated: ERROR: Couldn't attach to DCOP server! when backup.sh is launched by amanda.
I interpret this error to mean that amanda does not have rights to use dcop.
I, as user 1000 do, that command works without any reported error for me.
So, how do I add the backup group (or the user amanda) to the list of users who can access dcop and send kmail a msg?
Thanks.
Cheers, Gene Heskett
On Saturday 19 December 2020 08:34:37 am Gene Heskett via tde-users wrote:
On Saturday 19 December 2020 03:32:07 Gene Heskett wrote:
Now I need some cross permissions help.
I have added two dcop commands to my backup.sh that are: /opt/trinity/bin/dcop kmail KMailIface pauseBackgroundJobs and: /opt/trinity/bin/dcop kmail KMailIface resumeBackgroundJobs
But this script run as amanada, who is part of the backup group and this error or generated: ERROR: Couldn't attach to DCOP server! when backup.sh is launched by amanda.
So, how do I add the backup group (or the user amanda) to the list of users who can access dcop and send kmail a msg?
Hi Gene,
Thanks for posting the dcop commands, I’ve been meaning to add similar to my local nightly backup for awhile.
On the permissions issue:
Use sudo, basically the same as using sudo for yourusername to root, but replace root with yourusername and yourusername with amanada. And then get sudo to run without password.
- https://www.golinuxhub.com/2013/12/how-to-give-permission-to-user-to-run/ - https://linuxhandbook.com/sudo-without-password/
Straight su option? (I think this always wants password though): - https://unix.stackexchange.com/questions/372850/how-to-run-command-as-differ...
HTH, Michael
On Saturday 19 December 2020 11:15:43 am Michael via tde-users wrote:
On Saturday 19 December 2020 08:34:37 am Gene Heskett via tde-users wrote:
On Saturday 19 December 2020 03:32:07 Gene Heskett wrote:
Hi Gene,
Thanks for posting the dcop commands, I’ve been meaning to add similar to my local nightly backup for awhile.
On the permissions issue:
Use sudo, basically the same as using sudo for yourusername to root, but replace root with yourusername and yourusername with amanada. And then get sudo to run without password.
https://www.golinuxhub.com/2013/12/how-to-give-permission-to-user-to-run/ - https://linuxhandbook.com/sudo-without-password/
The two links* above Gene should do everything you need. There should be no need to dig into ICEauthority or anything else. Yes you'll need to edit the sudoers file, but there's plenty of google fu on how to do that.
Best, Michael
*In the second link see section: "Run only specific sudo commands without password"
On Saturday 19 December 2020 19:15:47 Michael via tde-users wrote:
On Saturday 19 December 2020 11:15:43 am Michael via tde-users wrote:
On Saturday 19 December 2020 08:34:37 am Gene Heskett via tde-users wrote:
On Saturday 19 December 2020 03:32:07 Gene Heskett wrote:
Hi Gene,
Thanks for posting the dcop commands, I’ve been meaning to add similar to my local nightly backup for awhile.
On the permissions issue:
Use sudo, basically the same as using sudo for yourusername to root, but replace root with yourusername and yourusername with amanada. And then get sudo to run without password.
https://www.golinuxhub.com/2013/12/how-to-give-permission-to-user-to -run/ - https://linuxhandbook.com/sudo-without-password/
This second URL showed me how to edit the sudoers file and add this:
amanda ALL=(ALL) NOPASSWD:/opt/trinity/bin/dcop
But it still fails: root@coyote:~$ su amanda -c "/opt/trinity/bin/dcop --user gene --all-sessions kmail KMailIface resumeBackgroundJobs" WARNING: ICE authority file /home/gene/.ICEauthorityis not readable by you! Please check permissions or set the $ICEAUTHORITY variable manually before calling dcop. [2020/12/19 20:16:00.554] DCOPClient::attachInternal. Attach failed Could not open network socket [2020/12/19 20:16:00.554] DCOPClient::attachInternal. Attach failed Could not open network socket ERROR: Couldn't attach to DCOP server! [2020/12/19 20:16:06.556] DCOPClient::attachInternal. Attach failed Could not open network socket [2020/12/19 20:16:12.557] DCOPClient::attachInternal. Attach failed Could not open network socket ERROR: Couldn't attach to DCOP server!
If I take out the --all-sessions, I get this: root@coyote:~$ su amanda -c "/opt/trinity/bin/dcop --user gene kmail KMailIface resumeBackgroundJobs" ERROR: Multiple available TDE sessions! Please specify the correct session to use with --session or use the --all-sessions option to broadcast to all sessions.
Which sounds like it might work if --session was named, but whats a "session"?
Thanks.
The two links* above Gene should do everything you need. There should be no need to dig into ICEauthority or anything else. Yes you'll need to edit the sudoers file, but there's plenty of google fu on how to do that.
Best, Michael
*In the second link see section: "Run only specific sudo commands without password" ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinity desktop.org
Cheers, Gene Heskett
On Sat, 19 Dec 2020 20:39:34 -0500 Gene Heskett via tde-users users@trinitydesktop.org wrote:
But it still fails: root@coyote:~$ su amanda -c "/opt/trinity/bin/dcop --user gene --all-sessions kmail KMailIface resumeBackgroundJobs" WARNING: ICE authority file /home/gene/.ICEauthorityis not readable by you! Please check permissions or set the $ICEAUTHORITY variable manually before calling dcop.
If you do the obvious, stupid (and likely insecure) thing and make /home/gene/.ICEauthority world-readable, does the command go through?
E. Liddell
On Saturday 19 December 2020 22:13:57 E. Liddell wrote:
On Sat, 19 Dec 2020 20:39:34 -0500
Gene Heskett via tde-users users@trinitydesktop.org wrote:
But it still fails: root@coyote:~$ su amanda -c "/opt/trinity/bin/dcop --user gene --all-sessions kmail KMailIface resumeBackgroundJobs" WARNING: ICE authority file /home/gene/.ICEauthorityis not readable by you! Please check permissions or set the $ICEAUTHORITY variable manually before calling dcop.
If you do the obvious, stupid (and likely insecure) thing and make /home/gene/.ICEauthority world-readable, does the command go through?
Doesn't seem to effect it. The previous strace showed that it never touched my .ICEauthority, but did look at my -rw-r--r-- 1 gene gene 53 Dec 3 01:41 .DCOPserver_coyote__0 which is world-readable, so I put my ICEauthority back to 0600. but now the strace isn't showing that any more.
What is the /etc/group/message-bus? dbus or dcop? neither?
E. Liddell ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinity desktop.org
Cheers, Gene Heskett
Dear Gene,
Am Sonntag, 20. Dezember 2020 schrieb Gene Heskett via tde-users:
On the permissions issue:
Use sudo, basically the same as using sudo for yourusername to root, but replace root with yourusername and yourusername with amanada. And then get sudo to run without password.
- https://www.golinuxhub.com/2013/12/how-to-give-permission-to-user -to -run/ - https://linuxhandbook.com/sudo-without-password/
This second URL showed me how to edit the sudoers file and add this:
amanda ALL=(ALL) NOPASSWD:/opt/trinity/bin/dcop
But it still fails: root@coyote:~$ su amanda -c "/opt/trinity/bin/dcop --user gene --all-sessions kmail
editing /etc/sudoers to my understanding has no effect on 'su' because the two are different things. I read this recently on debian-users, I think.
HTH
Kind regards, Stefan
On Sunday 20 December 2020 06:53:00 Stefan Krusche via tde-users wrote:
Dear Gene,
Am Sonntag, 20. Dezember 2020 schrieb Gene Heskett via tde-users:
On the permissions issue:
Use sudo, basically the same as using sudo for yourusername to root, but replace root with yourusername and yourusername with amanada. And then get sudo to run without password.
- https://www.golinuxhub.com/2013/12/how-to-give-permission-to-use r -to -run/ - https://linuxhandbook.com/sudo-without-password/
This second URL showed me how to edit the sudoers file and add this:
amanda ALL=(ALL) NOPASSWD:/opt/trinity/bin/dcop
But it still fails: root@coyote:~$ su amanda -c "/opt/trinity/bin/dcop --user gene --all-sessions kmail
editing /etc/sudoers to my understanding has no effect on 'su' because the two are different things. I read this recently on debian-users, I think.
So did I, and my recent experience seems to back that up. But I also had forgotten you have to reboot to make the logins aware of changes to sudoers, possibly my mistake?
After 22 years, I'm still learning the details of linux :-)
HTH
Kind regards, Stefan ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinity desktop.org
Cheers, Gene Heskett
On Saturday 19 December 2020 07:39:34 pm Gene Heskett via tde-users wrote:
On Saturday 19 December 2020 19:15:47 Michael via tde-users wrote:
On Saturday 19 December 2020 11:15:43 am Michael via tde-users wrote:
On Saturday 19 December 2020 08:34:37 am Gene Heskett via tde-users
wrote:
On Saturday 19 December 2020 03:32:07 Gene Heskett wrote:
Hi Gene,
Thanks for posting the dcop commands, I’ve been meaning to add similar to my local nightly backup for awhile.
On the permissions issue:
Use sudo, basically the same as using sudo for yourusername to root, but replace root with yourusername and yourusername with amanada. And then get sudo to run without password.
https://www.golinuxhub.com/2013/12/how-to-give-permission-to-user-to -run/ - https://linuxhandbook.com/sudo-without-password/
This second URL showed me how to edit the sudoers file and add this:
amanda ALL=(ALL) NOPASSWD:/opt/trinity/bin/dcop
But it still fails: root@coyote:~$ su amanda -c "/opt/trinity/bin/dcop --user gene --all-sessions kmail KMailIface resumeBackgroundJobs"
sudo NOT su... Read the first link, they go together... AFIK, you'll need to reformat the whole command for sudo (as it is not the same format as su).
Don't run as root either! Run it as plain amanda, even if you have to stick it in a test script and add it to amanda cron to kick it off.
Do use visudo to edit sudoers, it will use whatever editor* you have exported, e.g.:
export EDITOR=nano
* I know I’m a heathen heretic, I hate vi…
Best, Michael
On Sunday 20 December 2020 10:50:44 Michael via tde-users wrote:
On Saturday 19 December 2020 07:39:34 pm Gene Heskett via tde-users
wrote:
On Saturday 19 December 2020 19:15:47 Michael via tde-users wrote:
On Saturday 19 December 2020 11:15:43 am Michael via tde-users
wrote:
On Saturday 19 December 2020 08:34:37 am Gene Heskett via tde-users
wrote:
On Saturday 19 December 2020 03:32:07 Gene Heskett wrote:
Hi Gene,
Thanks for posting the dcop commands, I’ve been meaning to add similar to my local nightly backup for awhile.
On the permissions issue:
Use sudo, basically the same as using sudo for yourusername to root, but replace root with yourusername and yourusername with amanada. And then get sudo to run without password.
https://www.golinuxhub.com/2013/12/how-to-give-permission-to-use r-to -run/ - https://linuxhandbook.com/sudo-without-password/
This second URL showed me how to edit the sudoers file and add this:
amanda ALL=(ALL) NOPASSWD:/opt/trinity/bin/dcop
But it still fails: root@coyote:~$ su amanda -c "/opt/trinity/bin/dcop --user gene --all-sessions kmail KMailIface resumeBackgroundJobs"
sudo NOT su... Read the first link, they go together... AFIK, you'll need to reformat the whole command for sudo (as it is not the same format as su).
Don't run as root either! Run it as plain amanda, even if you have to stick it in a test script and add it to amanda cron to kick it off.
No, since they've built a paranoid security wall between me and anybody else, I'll run it as me.
Do use visudo to edit sudoers, it will use whatever editor* you have exported, e.g.:
export EDITOR=nano
- I know I’m a heathen heretic, I hate vi…
22 years ago I thought vi was the cats meow, then I found gedit, but gedit screwed me one too many times with its habit of 52 pickup file scrambling, so now I use nano or geany, neither has ever eaten my lunch, gedit has been banned, rm'd when I find pieces of it still sneaking around. vi I haven't used recently enough to even remember how to get in and out of the edit mode, or to save and quit. And typing help doesn't include those very vital commands. Or even how to close the help screen.
We used to have a saying in the amiga world, never ever allow the coder to write the docs, he is so familiar with how it works he thinks everyone is as familiar with it as he is, so the docs start with the rust spots on the gears, not with what the gears actually do. So we had another saying about when the code was finished, because somebody shot the coder.
The best language we ever had on the amiga was Arexx, but Bill Hawes, who wrote it, never got a dime from amiga, yet there was nothing the amiga could do that you couldn't do from an Arexx script.
The amigados, any version, never had a cron, but we needed to keep it busy in the middle of the night doing video production work, so Jim Hines and I wrote ezcron, in Arexx because it had a sleep command and didn't have to busywait. Not only that, we could calculate how long it had to sleep to wake up in the exact first tick of the next minute regardless of what time it was. We even used that to pop up a station ID in the first second of the hour. We even had a web page served up with an amiga, months before the major networks discovered it. Wasn't much, but you could dial it up and read the same teleprompter scripts our news anchors had read on the air 10 minutes before.
Being a medium market tv broadcaster was fun in those days 25 to 35 years ago.
Best, Michael ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinity desktop.org
Cheers, Gene Heskett
On Sunday 20 December 2020 09:02:15 Gene Heskett via tde-users wrote:
On Sunday 20 December 2020 10:50:44 Michael via tde-users wrote:
On Saturday 19 December 2020 07:39:34 pm Gene Heskett via tde-users
wrote:
On Saturday 19 December 2020 19:15:47 Michael via tde-users wrote:
On Saturday 19 December 2020 11:15:43 am Michael via tde-users
wrote:
On Saturday 19 December 2020 08:34:37 am Gene Heskett via tde-users
wrote:
On Saturday 19 December 2020 03:32:07 Gene Heskett wrote:
Hi Gene,
Thanks for posting the dcop commands, I’ve been meaning to add similar to my local nightly backup for awhile.
On the permissions issue:
Use sudo, basically the same as using sudo for yourusername to root, but replace root with yourusername and yourusername with amanada. And then get sudo to run without password.
https://www.golinuxhub.com/2013/12/how-to-give-permission-to-use r-to -run/ - https://linuxhandbook.com/sudo-without-password/
This second URL showed me how to edit the sudoers file and add this:
amanda ALL=(ALL) NOPASSWD:/opt/trinity/bin/dcop
But it still fails: root@coyote:~$ su amanda -c "/opt/trinity/bin/dcop --user gene --all-sessions kmail KMailIface resumeBackgroundJobs"
sudo NOT su... Read the first link, they go together... AFIK, you'll need to reformat the whole command for sudo (as it is not the same format as su).
Don't run as root either! Run it as plain amanda, even if you have to stick it in a test script and add it to amanda cron to kick it off.
No, since they've built a paranoid security wall between me and anybody else, I'll run it as me.
Do use visudo to edit sudoers, it will use whatever editor* you have exported, e.g.:
export EDITOR=nano
- I know I’m a heathen heretic, I hate vi…
22 years ago I thought vi was the cats meow, then I found gedit, but gedit screwed me one too many times with its habit of 52 pickup file scrambling, so now I use nano or geany, neither has ever eaten my lunch, gedit has been banned, rm'd when I find pieces of it still sneaking around. vi I haven't used recently enough to even remember how to get in and out of the edit mode, or to save and quit. And typing help doesn't include those very vital commands. Or even how to close the help screen.
We used to have a saying in the amiga world, never ever allow the coder to write the docs, he is so familiar with how it works he thinks everyone is as familiar with it as he is, so the docs start with the rust spots on the gears, not with what the gears actually do. So we had another saying about when the code was finished, because somebody shot the coder.
The best language we ever had on the amiga was Arexx, but Bill Hawes, who wrote it, never got a dime from amiga, yet there was nothing the amiga could do that you couldn't do from an Arexx script.
The amigados, any version, never had a cron, but we needed to keep it busy in the middle of the night doing video production work, so Jim Hines and I wrote ezcron, in Arexx because it had a sleep command and didn't have to busywait. Not only that, we could calculate how long it had to sleep to wake up in the exact first tick of the next minute regardless of what time it was. We even used that to pop up a station ID in the first second of the hour. We even had a web page served up with an amiga, months before the major networks discovered it. Wasn't much, but you could dial it up and read the same teleprompter scripts our news anchors had read on the air 10 minutes before.
Being a medium market tv broadcaster was fun in those days 25 to 35 years ago.
Best, Michael
Amiga, a blast from the past! That was my very first computer thingie, back in, um, 1984? But for me it was just a glorified typewriter, as I never saw the need to get geeky until I got on the Internet and had a few bad experiences, enough to wise up a little.
Bill
Anno domini 2020 Sun, 20 Dec 10:59:49 -0800 William Morder via tde-users scripsit:
[...] Amiga, a blast from the past! That was my very first computer thingie, back in, um, 1984? But for me it was just a glorified typewriter, as I never saw the need to get geeky until I got on the Internet and had a few bad experiences, enough to wise up a little.
Amiga without games? No BattleIsle? No Shadow of the Beast? Abomination! Heresy! ... Get out the the forks and torches!
Nik
Bill ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
On Sunday 20 December 2020 11:15:03 Dr. Nikolaus Klepp wrote:
Anno domini 2020 Sun, 20 Dec 10:59:49 -0800
William Morder via tde-users scripsit:
[...] Amiga, a blast from the past! That was my very first computer thingie, back in, um, 1984? But for me it was just a glorified typewriter, as I never saw the need to get geeky until I got on the Internet and had a few bad experiences, enough to wise up a little.
Amiga without games? No BattleIsle? No Shadow of the Beast? Abomination! Heresy! ... Get out the the forks and torches!
Nik
Bill
Oh, no -- there were games, but I was never much of a computer gamer. I tried Pac-Man when it came out, and a few others, I wasn't totally secluded from games. But my son pretty much wore out the keyboard and mouse on my Amiga, playing Defenders of the Crown. And I believe that was probably his introduction to computers, and now he's doing something start-uppity down in Austin, TX, so computer games can lead to good results, even if I don't have much use for them myself.
The same with porn; even if you don't watch it yourself, we pretty much owe most innovations in modern technology to porn. Or again, war (along with other catatrophes) drives most innovations in modern medicine, caused by the need to treat never-before-seen diseases or injuries.
But for me, a computer is still just a glorified typewriter, even though I now use it for many other things.
Bill
On Sunday 20 December 2020 13:59:49 William Morder via tde-users wrote:
On Sunday 20 December 2020 09:02:15 Gene Heskett via tde-users wrote:
On Sunday 20 December 2020 10:50:44 Michael via tde-users wrote:
On Saturday 19 December 2020 07:39:34 pm Gene Heskett via tde-users
wrote:
On Saturday 19 December 2020 19:15:47 Michael via tde-users
wrote:
On Saturday 19 December 2020 11:15:43 am Michael via tde-users
wrote:
On Saturday 19 December 2020 08:34:37 am Gene Heskett via tde-users
wrote:
> On Saturday 19 December 2020 03:32:07 Gene Heskett wrote:
Hi Gene,
Thanks for posting the dcop commands, I’ve been meaning to add similar to my local nightly backup for awhile.
On the permissions issue:
Use sudo, basically the same as using sudo for yourusername to root, but replace root with yourusername and yourusername with amanada. And then get sudo to run without password.
https://www.golinuxhub.com/2013/12/how-to-give-permission-to -use r-to -run/ - https://linuxhandbook.com/sudo-without-password/
This second URL showed me how to edit the sudoers file and add this:
amanda ALL=(ALL) NOPASSWD:/opt/trinity/bin/dcop
But it still fails: root@coyote:~$ su amanda -c "/opt/trinity/bin/dcop --user gene --all-sessions kmail KMailIface resumeBackgroundJobs"
sudo NOT su... Read the first link, they go together... AFIK, you'll need to reformat the whole command for sudo (as it is not the same format as su).
Don't run as root either! Run it as plain amanda, even if you have to stick it in a test script and add it to amanda cron to kick it off.
No, since they've built a paranoid security wall between me and anybody else, I'll run it as me.
Do use visudo to edit sudoers, it will use whatever editor* you have exported, e.g.:
export EDITOR=nano
- I know I’m a heathen heretic, I hate vi…
22 years ago I thought vi was the cats meow, then I found gedit, but gedit screwed me one too many times with its habit of 52 pickup file scrambling, so now I use nano or geany, neither has ever eaten my lunch, gedit has been banned, rm'd when I find pieces of it still sneaking around. vi I haven't used recently enough to even remember how to get in and out of the edit mode, or to save and quit. And typing help doesn't include those very vital commands. Or even how to close the help screen.
We used to have a saying in the amiga world, never ever allow the coder to write the docs, he is so familiar with how it works he thinks everyone is as familiar with it as he is, so the docs start with the rust spots on the gears, not with what the gears actually do. So we had another saying about when the code was finished, because somebody shot the coder.
The best language we ever had on the amiga was Arexx, but Bill Hawes, who wrote it, never got a dime from amiga, yet there was nothing the amiga could do that you couldn't do from an Arexx script.
The amigados, any version, never had a cron, but we needed to keep it busy in the middle of the night doing video production work, so Jim Hines and I wrote ezcron, in Arexx because it had a sleep command and didn't have to busywait. Not only that, we could calculate how long it had to sleep to wake up in the exact first tick of the next minute regardless of what time it was. We even used that to pop up a station ID in the first second of the hour. We even had a web page served up with an amiga, months before the major networks discovered it. Wasn't much, but you could dial it up and read the same teleprompter scripts our news anchors had read on the air 10 minutes before.
Being a medium market tv broadcaster was fun in those days 25 to 35 years ago.
Best, Michael
Amiga, a blast from the past! That was my very first computer thingie, back in, um, 1984? But for me it was just a glorified typewriter, as I never saw the need to get geeky until I got on the Internet and had a few bad experiences, enough to wise up a little.
We bought a block of 16 ipv4's back in about '86 when we started to use amiga's as graphics engines. Then we found the 192.168 xx.zz and dd-wrt while we never expanded what the world see's, are are now programming 8 tv channels out of a new tech room built since I retired in the middle of 2002. Using video servers Jim built from scratch. Running linux of course. They record 4 full hd channels, and play 4 channels each, simultaneously, 3 of them, with the third serving as a hot standby that can take over without missing a word should one of the two lose a drive in their raid arrays. That's self healing, just pull out the old drive and plug in a new one, ten minutes for the raid to put itself back together and its back in business. Then the owner died and his daughter sold it. The new people issued orders to get rid of linux and getting it all running on winders, which also never happened because the linux boxes just sat there and ran establishing their reason for existence in their uptimes. No bsod's, ever. We contracted with the weather channel for one of our channels wheb we went hidef digital in 2008. They built a sat rx facility in our back yard. filling it with windows junk. And wouldn't even give us a key so we could reboot it when it did a bsod. We didn't renew that contract as it was so bad, bsod'd 40% of the time and our sales people were being insulted over it.
But Jim could see the handwriting on the wall, so he is now the linux goto guy for triple the money the new brooms at the station offered at the fbi facility just north of Clarksburg. And my guess is that they will never have a Russian or Chinese access rumor like the rest of the fed agencies in bed with BG & winderz are trying to sweep under the rug at the moment. Its their wake up call, but bet the farm, NO heads will roll. They simply will not entertain that there actually IS a better way.
Most of the political hacks that run those agency's are MBA's, meaning they absolutely have to have somebody else to sue if it screws up, so they always buy IBM and Windows. IBM is decent hardware /most/ of the time, but winderz, Spit.
I own exactly one winderz box, an allinone that gets used as a smith chart display when I am re-tuning an AM broadcasting tower, a black art few of the yet living broadcast engineers understand, but I found a Vector Network Analyzer that actually does all the math to make a useable smith chart, in video or on paper for the FCC, live in near real time, made in Slovakia that I could afford and invested in it. Guys, all my age and older, using the original General Radio RF bridge gear spend a day collecting data, and another 2 days drawing that chart. make one adjustment, wash rinse and repeat. Sometimes for a month, I can now do it better, in one day. Whats not to like?
I have dd-wrt between me and the net, and I serve my web page from this machine. No one I didn't give credentials to, has come thru and had any access to my home system other than the bots mirroring my web pages content but I found a syntax error in my robots.txt file and much of that upload bandwidth wasting stuff has now been blocked.
The 4 main offenders in my iptables DROP list are all M$ owned, and the next 6 are googlebot's, both of which seem to ignore your robots.txt. And unlike fail2ban, which has yet to take any action after being restarted 2 weeks ago, I don't expire blocked addresses unless they send me a personal msg requesting it. That's happened once, I had so many hits from a place in northern kalipornia that I blocked them with a /16 where I block most with a /24, and he was a customer of theirs I already knew from a cnc mailing list.
Seen on a tee shirt for way too much money:
Don't piss off old folks, we're to old to fight, too slow to run, so we'll just kill you and be done with it. ;-)
Take care all. And Stay Well.
Bill ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinity desktop.org
Cheers, Gene Heskett
On Sunday 20 December 2020 16:54:40 Gene Heskett via tde-users wrote:
Now I am bumfuzzled.
I put those 2 commands in MY crontab since I can issue them without any errors.
But my crontab can't issue them. From an email I see this morning:
Cron gene@coyote /opt/trinity/bin/dcop kmail KMailIface resumeBackgroundJobs From: Cron Daemon root@coyote.coyote.den To: gene@coyote.coyote.den
ERROR: Couldn't attach to DCOP server! Two questions. And I'm starting to get pissed:
Why the hell is MY crontab sending me mail from root@coyote.den And if I can do it, why the hell can't MY crontab do it?
Thanks for any enlightenment.
Cheers, Gene Heskett
On Monday 21 December 2020 07:28:00 am Gene Heskett via tde-users wrote:
On Sunday 20 December 2020 16:54:40 Gene Heskett via tde-users wrote:
Now I am bumfuzzled.
I put those 2 commands in MY crontab since I can issue them without any errors.
But my crontab can't issue them. From an email I see this morning:
Cron gene@coyote /opt/trinity/bin/dcop kmail KMailIface resumeBackgroundJobs From: Cron Daemon root@coyote.coyote.den To: gene@coyote.coyote.den
ERROR: Couldn't attach to DCOP server! Two questions. And I'm starting to get pissed:
Why the hell is MY crontab sending me mail from root@coyote.den And if I can do it, why the hell can't MY crontab do it?
Thanks for any enlightenment.
No crontab knows about your $DISPLAY ;) . Check your display and add a line like I listed earlier.
AFAIK all email from crontabs send from root? (Well all my servers do, but check with someone who knows the guts of cron better than I.)
Best, Michael
On Monday 21 December 2020 09:41:12 Michael via tde-users wrote:
On Monday 21 December 2020 07:28:00 am Gene Heskett via tde-users
wrote:
On Sunday 20 December 2020 16:54:40 Gene Heskett via tde-users wrote:
Now I am bumfuzzled.
I put those 2 commands in MY crontab since I can issue them without any errors.
But my crontab can't issue them. From an email I see this morning:
Cron gene@coyote /opt/trinity/bin/dcop kmail KMailIface resumeBackgroundJobs From: Cron Daemon root@coyote.coyote.den To: gene@coyote.coyote.den
ERROR: Couldn't attach to DCOP server! Two questions. And I'm starting to get pissed:
Why the hell is MY crontab sending me mail from root@coyote.den And if I can do it, why the hell can't MY crontab do it?
Thanks for any enlightenment.
No crontab knows about your $DISPLAY ;) . Check your display and add a line like I listed earlier.
If successfull, there is no display. None needed
AFAIK all email from crontabs send from root? (Well all my servers do, but check with someone who knows the guts of cron better than I.)
I cannot setuid or seteuid, crontabs error checking says that a bad minute error. Do obviously that isn't how its done. Tomas was good enough to dig up some dcop docs but it appears that I'll have to write a script to wrap those commands up after setting up an env and registering with dcop each and every time I want to automate this. Docs by doxygen are best described as contaminated by excess verbiage. Hopefully I can find something usable.
Thanks Michael.
Best, Michael ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinity desktop.org
Cheers, Gene Heskett
On Monday 21 December 2020 10:05:11 Gene Heskett via tde-users wrote:
On Monday 21 December 2020 09:41:12 Michael via tde-users wrote:
On Monday 21 December 2020 07:28:00 am Gene Heskett via tde-users
wrote:
On Sunday 20 December 2020 16:54:40 Gene Heskett via tde-users wrote:
Now I am bumfuzzled.
I put those 2 commands in MY crontab since I can issue them without any errors.
But my crontab can't issue them. From an email I see this morning:
Cron gene@coyote /opt/trinity/bin/dcop kmail KMailIface resumeBackgroundJobs From: Cron Daemon root@coyote.coyote.den To: gene@coyote.coyote.den
ERROR: Couldn't attach to DCOP server! Two questions. And I'm starting to get pissed:
Why the hell is MY crontab sending me mail from root@coyote.den And if I can do it, why the hell can't MY crontab do it?
Thanks for any enlightenment.
No crontab knows about your $DISPLAY ;) . Check your display and add a line like I listed earlier.
If successfull, there is no display. None needed
AFAIK all email from crontabs send from root? (Well all my servers do, but check with someone who knows the guts of cron better than I.)
I cannot setuid or seteuid, crontabs error checking says that a bad minute error. Do obviously that isn't how its done. Tomas was good enough to dig up some dcop docs but it appears that I'll have to write a script to wrap those commands up after setting up an env and registering with dcop each and every time I want to automate this. Docs by doxygen are best described as contaminated by excess verbiage. Hopefully I can find something usable.
Thanks Michael.
Tomas@tuxstream.de dug up the docs for dcop at the kde 3.5 level, and that 8 pages of excess verbiage may contain the seeds that will make it work. The question then is: has anything significant been changed in the tde version?
Thanks Michael.
Cheers, Gene Heskett
On Sunday 20 December 2020 11:02:15 am Gene Heskett via tde-users wrote:
On Sunday 20 December 2020 10:50:44 Michael via tde-users wrote:
On Saturday 19 December 2020 07:39:34 pm Gene Heskett via tde-users
wrote:
On Saturday 19 December 2020 19:15:47 Michael via tde-users wrote:
On Saturday 19 December 2020 11:15:43 am Michael via tde-users
wrote:
On Saturday 19 December 2020 08:34:37 am Gene Heskett via tde-users
wrote:
On Saturday 19 December 2020 03:32:07 Gene Heskett wrote:
Hi Gene,
Thanks for posting the dcop commands, I’ve been meaning to add similar to my local nightly backup for awhile.
On the permissions issue:
Use sudo, basically the same as using sudo for yourusername to root, but replace root with yourusername and yourusername with amanada. And then get sudo to run without password.
https://www.golinuxhub.com/2013/12/how-to-give-permission-to-use r-to -run/ - https://linuxhandbook.com/sudo-without-password/
This second URL showed me how to edit the sudoers file and add this:
amanda ALL=(ALL) NOPASSWD:/opt/trinity/bin/dcop
But it still fails: root@coyote:~$ su amanda -c "/opt/trinity/bin/dcop --user gene --all-sessions kmail KMailIface resumeBackgroundJobs"
sudo NOT su... Read the first link, they go together... AFIK, you'll need to reformat the whole command for sudo (as it is not the same format as su).
Don't run as root either! Run it as plain amanda, even if you have to stick it in a test script and add it to amanda cron to kick it off.
No, since they've built a paranoid security wall between me and anybody else, I'll run it as me.
Well, that is sucky :(
For the display issues earlier, try one of these:
export DISPLAY=:0 export DISPLAY=:0.0
Under your username do:
echo $DISPLAY
and I’m guessing use that. Mine is “:0”, the :0.0 was used in a cron entry itself*, so probably not the one to use.
This is from an old bash script I ran in root cron that needed to also start something as myself. It was on a Ubuntu 14.04 box, it’s Debian based but might not be the exact syntax anymore.
export DISPLAY=:0 sudo -H -u michael bash -c '/usr/bin/progname &'
As long as you have the right sudoers entry (it looked like you had way overkill, but it should work), running the same in the amanda script should work. I’ll guess this should be the full syntax of the lines you need:
export DISPLAY=:0 sudo -H -u gene bash -c '/opt/trinity/bin/dcop kmail KMailIface pauseBackgroundJobs'
do backup stuff<<
sudo -H -u gene bash -c '/opt/trinity/bin/dcop kmail KMailIface resumeBackgroundJobs'
HTH, Michael
* Cron entry was like: export DISPLAY=:0.0 ; /home/michael/common/bin/bashscript.sh
On Sunday 20 December 2020 15:07:26 Michael via tde-users wrote:
On Sunday 20 December 2020 11:02:15 am Gene Heskett via tde-users wrote:
On Sunday 20 December 2020 10:50:44 Michael via tde-users wrote:
On Saturday 19 December 2020 07:39:34 pm Gene Heskett via tde-users
wrote:
On Saturday 19 December 2020 19:15:47 Michael via tde-users wrote:
On Saturday 19 December 2020 11:15:43 am Michael via tde-users
wrote:
On Saturday 19 December 2020 08:34:37 am Gene Heskett via tde-users
wrote:
> On Saturday 19 December 2020 03:32:07 Gene Heskett wrote:
Hi Gene,
Thanks for posting the dcop commands, I’ve been meaning to add similar to my local nightly backup for awhile.
On the permissions issue:
Use sudo, basically the same as using sudo for yourusername to root, but replace root with yourusername and yourusername with amanada. And then get sudo to run without password.
https://www.golinuxhub.com/2013/12/how-to-give-permission-to -use r-to -run/ - https://linuxhandbook.com/sudo-without-password/
This second URL showed me how to edit the sudoers file and add this:
amanda ALL=(ALL) NOPASSWD:/opt/trinity/bin/dcop
But it still fails: root@coyote:~$ su amanda -c "/opt/trinity/bin/dcop --user gene --all-sessions kmail KMailIface resumeBackgroundJobs"
sudo NOT su... Read the first link, they go together... AFIK, you'll need to reformat the whole command for sudo (as it is not the same format as su).
Don't run as root either! Run it as plain amanda, even if you have to stick it in a test script and add it to amanda cron to kick it off.
No, since they've built a paranoid security wall between me and anybody else, I'll run it as me.
Well, that is sucky :(
For the display issues earlier, try one of these:
export DISPLAY=:0 export DISPLAY=:0.0
Under your username do:
echo $DISPLAY
and I’m guessing use that. Mine is “:0”, the :0.0 was used in a cron entry itself*, so probably not the one to use.
This is from an old bash script I ran in root cron that needed to also start something as myself. It was on a Ubuntu 14.04 box, it’s Debian based but might not be the exact syntax anymore.
export DISPLAY=:0 sudo -H -u michael bash -c '/usr/bin/progname &'
As long as you have the right sudoers entry (it looked like you had way overkill, but it should work), running the same in the amanda script should work.
That entry, previously shown in this thread was an sudoers killing syntax error, so its been removed. thanks to having more than one root session going at the time.
I’ll guess this should be the full syntax of the lines you need:
export DISPLAY=:0
probably not needed, these scripts normally only send emails.
sudo -H -u gene bash -c '/opt/trinity/bin/dcop kmail KMailIface pauseBackgroundJobs'
how about, since the commands are already defined above it: sudo -H -u gene bash -c "$Cmdholdit" ? etc. or "$Cmdresume" at the end?
do backup stuff<<
sudo -H -u gene bash -c '/opt/trinity/bin/dcop kmail KMailIface resumeBackgroundJobs'
HTH, Michael
But it doesn't work, its asking for amanda's pw and there isn't one.
Here is what I did: root@coyote:~$ su amanda amanda@coyote:/root$ echo $Cmdresume
amanda@coyote:/root$ Cmdresume="/opt/trinity/bin/dcop kmail KMailIface resumeBackgroundJobs" amanda@coyote:/root$ echo $Cmdresume /opt/trinity/bin/dcop kmail KMailIface resumeBackgroundJobs amanda@coyote:/root$ sudo -H -u gene bash -c $Cmdresume
We trust you have received the usual lecture from the local System Administrator. It usually boils down to these three things:
#1) Respect the privacy of others. #2) Think before you type. #3) With great power comes great responsibility.
[sudo] password for amanda: Sorry, try again. [sudo] password for amanda: So I'll just do it from my own crontab, holding the background stuff for an hour 31 while amanda is running. Like this: 59 1 * * * /opt/trinity/bin/dcop kmail KMailIface pauseBackgroundJobs 30 3 * * * /opt/trinity/bin/dcop kmail KMailIface resumeBackgroundJobs
And we'll see if that works.
- Cron entry was like:
export DISPLAY=:0.0 ; /home/michael/common/bin/bashscript.sh
tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinity desktop.org
Cheers, Gene Heskett
On Saturday 19 of December 2020 15:34:37 Gene Heskett via tde-users wrote:
On Saturday 19 December 2020 03:32:07 Gene Heskett wrote:
Now I need some cross permissions help.
I have added two dcop commands to my backup.sh that are: /opt/trinity/bin/dcop kmail KMailIface pauseBackgroundJobs and: /opt/trinity/bin/dcop kmail KMailIface resumeBackgroundJobs
Specified as Cmdholdit and Cmdresume
and called as $Comdholdit and $Cmdresume
But this script run as amanada, who is part of the backup group and this error or generated: ERROR: Couldn't attach to DCOP server! when backup.sh is launched by amanda.
I interpret this error to mean that amanda does not have rights to use dcop.
I, as user 1000 do, that command works without any reported error for me.
So, how do I add the backup group (or the user amanda) to the list of users who can access dcop and send kmail a msg?
Thanks.
Cheers, Gene Heskett
Hi Gene,
to communicate with the DCOP server, authentication using the ICE authority key is required. When you normally run a dcop command like the one you used it, the ICE authority key for the current user is searched. Because this is a different user than the one under which KMail is running, you need to handle it.
If the user under which the backup is running has sufficient privileges, you can try adding the --all-users --all-sessions parameters for dcop.
Cheers
On Saturday 19 December 2020 12:34:12 Slávek Banko via tde-users wrote:
On Saturday 19 of December 2020 15:34:37 Gene Heskett via tde-users
wrote:
On Saturday 19 December 2020 03:32:07 Gene Heskett wrote:
Now I need some cross permissions help.
I have added two dcop commands to my backup.sh that are: /opt/trinity/bin/dcop kmail KMailIface pauseBackgroundJobs and: /opt/trinity/bin/dcop kmail KMailIface resumeBackgroundJobs
Specified as Cmdholdit and Cmdresume
and called as $Comdholdit and $Cmdresume
But this script run as amanada, who is part of the backup group and this error or generated: ERROR: Couldn't attach to DCOP server! when backup.sh is launched by amanda.
I interpret this error to mean that amanda does not have rights to use dcop.
I, as user 1000 do, that command works without any reported error for me.
So, how do I add the backup group (or the user amanda) to the list of users who can access dcop and send kmail a msg?
Thanks.
Cheers, Gene Heskett
Hi Gene,
to communicate with the DCOP server, authentication using the ICE authority key is required. When you normally run a dcop command like the one you used it, the ICE authority key for the current user is searched. Because this is a different user than the one under which KMail is running, you need to handle it.
If the user under which the backup is running has sufficient privileges, you can try adding the --all-users --all-sessions parameters for dcop.
But when I tried to do that, no action was made, and the help page has not been written. So despite that now showing up in kdcop, amanda still cannot perform because amanda can't contact the server, but I can.
So some more hand holding is needed. :) Like how, short of rebooting, do I enable a restart of dcop? Mmmm, ack the manpage can I add --user gene in the middle of that Cmdline?
So, poking at the sleeping giant with this is as far as I want to go without better guidance:
root@coyote:bin$ su amanda -c "/opt/trinity/bin/dcop --user gene --all-sessions kmail KMailIface pauseBackgroundJobs" WARNING: ICE authority file /home/gene/.ICEauthorityis not readable by you! Please check permissions or set the $ICEAUTHORITY variable manually before calling dcop. [2020/12/19 13:35:38.922] DCOPClient::attachInternal. Attach failed Could not open network socket [2020/12/19 13:35:38.922] DCOPClient::attachInternal. Attach failed Could not open network socket ERROR: Couldn't attach to DCOP server! [2020/12/19 13:35:44.924] DCOPClient::attachInternal. Attach failed Could not open network socket [2020/12/19 13:35:50.925] DCOPClient::attachInternal. Attach failed Could not open network socket ERROR: Couldn't attach to DCOP server!
help?
Thanks.
Cheers
Cheers, Gene Heskett
On Saturday 19 December 2020 12:38:52 pm Gene Heskett via tde-users wrote:
On Saturday 19 December 2020 12:34:12 Slávek Banko via tde-users wrote:
On Saturday 19 of December 2020 15:34:37 Gene Heskett via tde-users
On Saturday 19 December 2020 03:32:07 Gene Heskett wrote:
Now I need some cross permissions help.
So, poking at the sleeping giant with this is as far as I want to go without better guidance:
root@coyote:bin$ su amanda -c "/opt/trinity/bin/dcop --user gene --all-sessions kmail KMailIface pauseBackgroundJobs" WARNING: ICE authority file /home/gene/.ICEauthorityis not readable by you! Please check permissions or set the $ICEAUTHORITY variable manually before calling dcop. [2020/12/19 13:35:38.922] DCOPClient::attachInternal. Attach failed Could not open network socket [2020/12/19 13:35:38.922] DCOPClient::attachInternal. Attach failed Could not open network socket ERROR: Couldn't attach to DCOP server! [2020/12/19 13:35:44.924] DCOPClient::attachInternal. Attach failed Could not open network socket [2020/12/19 13:35:50.925] DCOPClient::attachInternal. Attach failed Could not open network socket ERROR: Couldn't attach to DCOP server!
help?
Did the sudo instructions I sent not work? What were the errors?
Best, Michael
On Saturday 19 December 2020 17:41:53 Michael via tde-users wrote:
On Saturday 19 December 2020 12:38:52 pm Gene Heskett via tde-users
wrote:
On Saturday 19 December 2020 12:34:12 Slávek Banko via tde-users
wrote:
On Saturday 19 of December 2020 15:34:37 Gene Heskett via tde-users
On Saturday 19 December 2020 03:32:07 Gene Heskett wrote:
Now I need some cross permissions help.
So, poking at the sleeping giant with this is as far as I want to go without better guidance:
root@coyote:bin$ su amanda -c "/opt/trinity/bin/dcop --user gene --all-sessions kmail KMailIface pauseBackgroundJobs" WARNING: ICE authority file /home/gene/.ICEauthorityis not readable by you! Please check permissions or set the $ICEAUTHORITY variable manually before calling dcop. [2020/12/19 13:35:38.922] DCOPClient::attachInternal. Attach failed Could not open network socket [2020/12/19 13:35:38.922] DCOPClient::attachInternal. Attach failed Could not open network socket ERROR: Couldn't attach to DCOP server! [2020/12/19 13:35:44.924] DCOPClient::attachInternal. Attach failed Could not open network socket [2020/12/19 13:35:50.925] DCOPClient::attachInternal. Attach failed Could not open network socket ERROR: Couldn't attach to DCOP server!
help?
Did the sudo instructions I sent not work? What were the errors?
sudo and su are two different critters, and for amanda to access my /home dir would first need a sudo -i and the PW to become root, followed by the su gene -c "command" to execute the command line. I don't think amanda even has a pw set. Its a user ok, but only because I configure and build amanda in that sub-directory
Best, Michael ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinity desktop.org
Cheers, Gene Heskett
-
Dr. Nikolaus Klepp -
E. Liddell -
Gene Heskett -
Michael -
Slávek Banko -
Stefan Krusche -
William Morder