Its been a null output in the previous script, Dint see any such kind of errors. But i slightly modified the script and popped up with some errors. I'm seeing the functions are not getting executed properly, instead errors were found.
Zaxxon,
I set the script to run into debug mode, but Im unable to trace the real errors .
i am new to solaris
i have one module which contain certain header files and sub modules
i want ot execute the module and c what the values are beeing assigned to variables
is makefile only solution for this
is there any editor to help it,so that i can c the flow of the program and also... (1 Reply)
Hi,
In our program, we are using SIGTERM and i tired to put break point in this function. But my debuger is unable to brake at that point.
I am working on Mac X and using XCode.
Thanks (0 Replies)
Hi,
In our program, we are using SIGTERM and i tired to put break point in this function. But my debuger is unable to brake at that point.
I am working on Mac X and using XCode.
Thanks (1 Reply)
When I run a lengthy script in debug mode i need to capture all the steps which are executed.
e.g
ksh -x script.ksh
+ test -f /proc/mounts
+ /bin/ls -l /proc/21326/exe
+ is=ksh
+ test ksh = ksh
+ test -s /etc/ksh.kshrc
+ . /etc/ksh.kshrc
+ trap 1 2 3
+ who am i
+ awk {print $1}
+... (2 Replies)
Hi All,
I have a question on debugging the .so file.
When I am running makefile I am getting a .so file and we are using that .so file for executing our code.But I want to know
1.Can I use dbx or gdb to debug a .so file?
2.How can i generate .out file so that i can use that in dbx or gdb... (1 Reply)
Can you help please ?
./get_df.sh: syntax error at line 13 : `then' unexpected
#!/bin/ksh
while :
do
PER=`df -h /DATA/ | nawk '{if (NR != 1) { sub (/%/,""); print $(NF-1)}}'`
if
then
if]
then
mailx -s "FS over 90 per" me@company.com
touch... (2 Replies)
Hello, I was looking at kernel log's and found some parts what was "interesting"
I previously started looking what has been going on in my computer because I had hacker attacks on my machine.
Installed Avira & Little Snitch - softwares
Previously my computer opened few folders what I have... (1 Reply)
How can I debug this script?
I want to know what it is doing or not doing?
#!/bin/bash
#
#
if ; then
# Do the thing you want before suspend here
echo "we are suspending." > /tmp/systemd_suspend_test.txt
elif ; then
# Do the thing you want after resume here
echo "and we are... (21 Replies)
Discussion started by: drew77
21 Replies
LEARN ABOUT SUNOS
startx
STARTX(1) General Commands Manual STARTX(1)NAME
startx - initialize an X session
SYNOPSIS
startx [ [ client ] options ... ] [ -- [ server ] [ display ] options ... ]
DESCRIPTION
The startx script is a front end to xinit(1) that provides a somewhat nicer user interface for running a single session of the X Window
System. It is often run with no arguments.
Arguments immediately following the startx command are used to start a client in the same manner as xinit(1). The special argument '--'
marks the end of client arguments and the beginning of server options. It may be convenient to specify server options with startx to
change on a per-session basis the default color depth, the server's notion of the number of dots-per-inch the display device presents, or
take advantage of a different server layout, as permitted by the Xorg(1) server and specified in the xorg.conf(5) configuration. Some
examples of specifying server arguments follow; consult the manual page for your X server to determine which arguments are legal.
startx -- -depth 16
startx -- -dpi 100
startx -- -layout Multihead
To determine the client to run, startx first looks for a file called .xinitrc in the user's home directory. If that is not found, it uses
the file xinitrc in the xinit library directory. If command line client options are given, they override this behavior and revert to the
xinit(1) behavior. To determine the server to run, startx first looks for a file called .xserverrc in the user's home directory. If that
is not found, it uses the file xserverrc in the xinit library directory. If command line server options are given, they override this
behavior and revert to the xinit(1) behavior. Users rarely need to provide a .xserverrc file. See the xinit(1) manual page for more
details on the arguments.
The system-wide xinitrc and xserverrc files are found in the /etc/X11/xinit directory.
ENVIRONMENT VARIABLES
DISPLAY This variable gets set to the name of the display to which clients should connect. Note that this gets set, not
read.
XAUTHORITY This variable, if not already defined, gets set to $(HOME)/.Xauthority. This is to prevent the X server, if not
given the -auth argument, from automatically setting up insecure host-based authentication for the local host.
See the Xserver(1) and Xsecurity(7) manual pages for more information on X client/server authentication.
FILES
$(HOME)/.xinitrc Client to run. Typically a shell script which runs many programs in the background.
$(HOME)/.xserverrc Server to run. The default is X.
/etc/X11/xinit/xinitrc Client to run if the user has no .xinitrc file.
/etc/X11/xinit/xserverrc Server to run if the user has no .xserverrc file.
SEE ALSO xinit(1), X(7), Xserver(1), Xorg(1), xorg.conf(5)X Version 11 xinit 1.3.2 STARTX(1)