Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Its running the script as log files are being completed, but it doent opent a xterm terminal, neither a konsole terminal. When I use run-parts for testing it, It does open the terminals...
#!/bin/sh
#
PATH=/sbin:/bin:/usr/sbin:/usr/bin
export PATH
fechaname=hardback-`date +%Y-%m-%d_%H:%M:%S`.log
su myuser -c "/home/myuser/scripts/hardback.sh" | tee /home/myuser/LINUXDEBS/NOBACKUP/logs/$fechaname
su myuser -c "konsole --hold -e more /home/myuser/LINUXDEBS/NOBACKUP/logs/$fechaname"
su myuser -c "xterm -hold -e more /home/myuser/LINUXDEBS/NOBACKUP/logs/$fechaname"
Any help? , Thanks
Last edited by bester69 on 2018-06-22 10:21, edited 1 time in total.
bester69 wrote:STOP 2030 globalists demons, keep the fight for humanity freedom against NWO...
bester69 wrote:Its running the script as log files are being completed, but it doent opent a xterm terminal, neither a konsole terminal. When I use run-parts for testing it, It does open the terminals... :?: :?:
#!/bin/sh
#
PATH=/sbin:/bin:/usr/sbin:/usr/bin
export PATH
fechaname=hardback-`date +%Y-%m-%d_%H:%M:%S`.log
su myuser -c "/home/myuser/scripts/hardback.sh" | tee /home/myuser/LINUXDEBS/NOBACKUP/logs/$fechaname
su myuser -c "konsole --hold -e more /home/myuser/LINUXDEBS/NOBACKUP/logs/$fechaname"
su myuser -c "xterm -hold -e more /home/myuser/LINUXDEBS/NOBACKUP/logs/$fechaname"
Any help? :( , Thanks
Well cron.daily runs as root so I don't know how you expect that to work (hint: imagine nobody is logged in, where should xterm show up?).
cron is not (designed) for interactive things. If you really insist in (ab)using it for that purpose, use at least the user's cron, so that you don't need the "su myuser -c".
Note also that before konsole or xterm can do anything graphical they need to know where they are supposed to show up, i.e. at the very least you should set the DISPLAY environment variable to something sensible.
On top you have the whole session/dbus/pam/systemd/policykit mess to deal with. But first things first.. (it won't work anyway).
reinob wrote:
Well cron.daily runs as root so I don't know how you expect that to work (hint: imagine nobody is logged in, where should xterm show up?).
cron is not (designed) for interactive things. If you really insist in (ab)using it for that purpose, use at least the user's cron, so that you don't need the "su myuser -c".
Note also that before konsole or xterm can do anything graphical they need to know where they are supposed to show up, i.e. at the very least you should set the DISPLAY environment variable to something sensible.
On top you have the whole session/dbus/pam/systemd/policykit mess to deal with. But first things first.. (it won't work anyway).
Thanks for answering, I think DISPLAY environment will work, It had already triggered xterm and konsole in a test script.