1. Rsyslog config file
2. edit /etc/quantum/quantum.conf
use_syslog = true
syslog_log_facility = LOG_USER
3. rsyslogd restart
service rsyslog restart
sudo apt-get install gcc g++ python
adjust /var/lib/quantum directory permission
sh> chmod o+w /var/lib/quantum
log_format = %(asctime)s %(levelname)8s %(filename)s %(funcName)s [%(name)s] [%(message)s
sh> script /dev/null
1. The host (jsmith) then has to allow multiuser access in the screen session via the command CTRL-A :multiuser on (all 'screen' commands start with the screen escape sequence, CTRL-A).
2. Next, the host (jsmith) must grant permission to the remote user (bjones) to access the screen session using the commadn CTRL-A :acladd user_name where user_name is the remote user's login ID.
3. The remote user can now connect to the hosts 'screen' session. The syntax to connect to another user's screen session is screen -x host_username/sessionname.
screen -x jsmith/screen-test
Attached is a screenshot of 2 computers "sharing" the same terminal session.
What is most tedious but difficult thing in using oozie?
Maybe that’s ‘Time zone’ and related things.
but you should know that oozie server only using UTC based time zone though you set your localtime zone. ( that means if you don't use 3.3.0 or later, you always see UTC base clock).
then how could you make your workflow working at your time zone?
the secret is 'tzOffset()' variables.
First, setting workflow application time as UTC then setting dataset timezone as your timezone. Lastly setting 'tzOffset()/60' to your event setting.
| • |