10-23-2019
i am a express application assembler
hi,
windowsmanager ? What does it matter ? The EXE must RUN ! RUN !
For myself. I program single short applications that RUN immediatelly.
code / GUI / Network READY.
Only application - only for Linux. NOTHING ELSE.
Tequila on the beach.
10 More Discussions You Might Find Interesting
1. Programming
I am a newbie to the *nix developer community, and was wondering if anyone has any good links on the subject of GUI programming in the X environment. Any suggestion is welcome =). (2 Replies)
Discussion started by: Solitare
2 Replies
2. Programming
Do you think that Motif programming is old...should I learn it... (3 Replies)
Discussion started by: CreamHarry
3 Replies
3. Programming
Hi everyone, I am new in motif programming and I want to learn how to program it. I use Fedora core 3 and every time I compile the program, there are always some errors appear. One of the errors said that I do not have the Xm/xxxx.h However, I do not know precisely how to install header files. I... (0 Replies)
Discussion started by: qqq
0 Replies
4. UNIX for Dummies Questions & Answers
Hello all,
1) I want to have a GUI application that will call Unix shell scripts,
2) that GUI application should be able to reside on windows ( if possible) and then call Unix shell script either directly or through a server residing on unix.
That is for example.
If a is windows gui (... (1 Reply)
Discussion started by: hchivukula
1 Replies
5. Solaris
An application was getting built using Motif 1.2 that used come along Solaris 6 OS for compiling and linking. Application is run using Motif 2.1 on Solaris 10 and it is working fine.
Application compilation and linking is working fine on Solaris 10 with Motif 2.1.0 but running the application... (0 Replies)
Discussion started by: shafi2all
0 Replies
6. Programming
python gui or c++ gui or java gui?
and when to use etch one? (1 Reply)
Discussion started by: kaja
1 Replies
7. Programming
Hi there ,
i am interesting in MOTIF programming.
One question :
Is it right that in Motif GUI programming the actions are automaticly transformed and networked to other clients over the internet without network programming necessary ?
Are the commands automatic transformed by the X11... (4 Replies)
Discussion started by: Zabo
4 Replies
8. UNIX for Beginners Questions & Answers
Hi ,
wanna learn native GUI programming in Unix-Linux instead of Gtk and Qt.
No problem. You don't need a cross platform Gui toolkit like Gtk and Qt.
And the code and syntax is also not more or less than others.
Check out this code for a simple mainwindow for your application that is openend in... (0 Replies)
Discussion started by: Sennenmut
0 Replies
9. UNIX for Beginners Questions & Answers
I'll be a professional MOTIF GUI programmer.
And nothing will stop me. Nothing.
:) (5 Replies)
Discussion started by: Sennenmut
5 Replies
10. UNIX for Beginners Questions & Answers
Motif GUI example. Unix executable ready.
Hi ,
i have attached my executable GUI example file in form of a .gz file.
please gunzip file before.
May i ask you for check it out that it is running on your machine ?
You should have "Motif" package installed.
when you klick the unix executable... (4 Replies)
Discussion started by: Sennenmut
4 Replies
LEARN ABOUT CENTOS
systemd-run
SYSTEMD-RUN(1) systemd-run SYSTEMD-RUN(1)
NAME
systemd-run - Run programs in transient scope or service units
SYNOPSIS
systemd-run [OPTIONS...] COMMAND [ARGS...]
DESCRIPTION
systemd-run may be used to create and start a transient .service or a .scope unit and run the specified COMMAND in it.
If a command is run as transient service unit, it will be started and managed by the service manager like any other service, and thus show
up in the output of systemctl list-units like any other unit. It will run in a clean and detached execution environment. systemd-run will
start the service asynchronously in the background and immediately return.
If a command is run as transient scope unit, it will be started directly by systemd-run and thus inherit the execution environment of the
caller. It is however managed by the service manager similar to normal services, and will also show up in the output of systemctl
list-units. Execution in this case is synchronous, and execution will return only when the command finishes.
OPTIONS
The following options are understood:
-h, --help
Prints a short help text and exits.
--version
Prints a short version string and exits.
--user
Talk to the service manager of the calling user, rather than the service manager of the system.
--system
Talk to the service manager of the system. This is the implied default.
--scope
Create a transient .scope unit instead of the default transient .service unit.
--unit=
Use this unit name instead of an automatically generated one.
--description=
Provide description for the unit. If not specified, the command itself will be used as a description. See Description= in
systemd.unit(5).
--slice=
Make the new .service or .scope unit part of the specified slice, instead of the system.slice.
--remain-after-exit
After the service's process has terminated, keep the service around until it is explicitly stopped. This is useful to collect runtime
information about the service after it finished running. Also see RemainAfterExit= in systemd.service(5).
--send-sighup
When terminating the scope unit, send a SIGHUP immediately after SIGTERM. This is useful to indicate to shells and shell-like processes
that the connection has been severed. Also see SendSIGHUP= in systemd.kill(5).
All command-line arguments after the first non-option argument become part of the commandline of the launched process. If a command is run
as service unit, its first argument needs to be an absolute binary path.
EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise.
EXAMPLE
The following command will log the environment variables provided by systemd to services:
# systemd-run env
Running as unit run-19945.service.
# journalctl -u run-19945.service
Sep 08 07:37:21 bupkis systemd[1]: Starting /usr/bin/env...
Sep 08 07:37:21 bupkis systemd[1]: Started /usr/bin/env.
Sep 08 07:37:21 bupkis env[19948]: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
Sep 08 07:37:21 bupkis env[19948]: LANG=en_US.UTF-8
Sep 08 07:37:21 bupkis env[19948]: BOOT_IMAGE=/vmlinuz-3.11.0-0.rc5.git6.2.fc20.x86_64
SEE ALSO
systemd(1), systemctl(1), systemd.unit(5), systemd.service(5), systemd.scope(5), systemd.slice(5).
systemd 208 SYSTEMD-RUN(1)