10 More Discussions You Might Find Interesting
1. Solaris
Hi all
I am facing difficulties when using the useraddcommand.
when running useradd -u 60006 -g 100 -d /opt/xxx/yyy/z -m -s /bin/false ftpuser
It does create the user, but with a wrong home directory. It creates its home directory at /home/ftpuser
Please can you help? (2 Replies)
Discussion started by: fretagi
2 Replies
2. Forum Support Area for Unregistered Users & Account Problems
Hi.
I registered, but when trying to post, I get ...
"Sorry, you do not have enough Bits to post a new thread"
Google & Forum search showed some hits, but no solution.
Please advide.
Thanks! (1 Reply)
Discussion started by: gehe
1 Replies
3. AIX
Hi everyone!
Ok so I'm trying for the first time to install AIX on a LPAR with NIM.
The NIM:
root@oaexpnimp01(/home/root) # oslevel -s
6100-08-02-1316
I'm trying to install AIX 6.1 TL1. I successfully created a new lpp source
root@oaexpnimp01(/home/root) # lsnim -l AIX61_TL1_2... (10 Replies)
Discussion started by: trivium012
10 Replies
4. Programming
Hi I am new to QT.I am running Qt 4.7 on Fedora 9.My Application crashes with the the following statements. on execution of
return app.exec();
The inferior stopped because it received a signal from the Operating System.
Signal name : SIGSEGV
Signal meaning :Segmentation fault:wall:
... (2 Replies)
Discussion started by: sruthihsr
2 Replies
5. Solaris
Hi All,
I am trying to create a folder in /export/home/user1 directory as a user1 but I am getting the error message as
-bash-3.00$ mkdir abc
mkdir: Failed to make directory "abc"; Permission denied
Also I tried creating the folder but it fails too
-bash-3.00$ touch abc
touch: cannot... (2 Replies)
Discussion started by: Manjunath K V
2 Replies
6. Solaris
Hi,
can someone help with the following?
I got 1x146GB disk which is span by just one zfs rpool.
When issue for example:
as you can see in above output the flar is very small, just around 10KB
rpool with all data sets has several GB so this can't be good image. This is on the Solaris 10... (3 Replies)
Discussion started by: TomSu
3 Replies
7. Solaris
In a Solaris9 environment I'm trying to restore flash archive (flar) with SVM mirrored devices to same server via jumpstart server and it is failing to create boot file and drops down to a command prompt in single user mode, metastat -i and metastat -p output looks good when compared to the ones... (0 Replies)
Discussion started by: mbak
0 Replies
8. HP-UX
Hi,
I have a process which creates pthreads to generate some reports. After creating the reports these threads return null. But after 1024 threads, the process is not able to create any threads further.,and at max 5 threads are existing simultaneously and are returning the control back after... (2 Replies)
Discussion started by: Krsh
2 Replies
9. UNIX for Dummies Questions & Answers
I am using Solaris 9 machine. I am unable to create any aliases.
I gave the following command:
alias ls='ls -ltr'
It did nt give any errors. But next time, I use ls, it is working simply as ls but not like ls -ltr.
I am not having admin permissions. Is it the reason. (3 Replies)
Discussion started by: mumashankar
3 Replies
10. AIX
Hi,
I'm trying to create a new group on an AIX 5.2.0.0. server but am getting the following error:
root:/root $ mkgroup debt
3004-698 Error committing changes to "debt" : Value is invalid.
I've change the group name to no affect.
Does anyone have any ideas what could be causing this?
... (0 Replies)
Discussion started by: m223464
0 Replies
LEARN ABOUT OPENSOLARIS
lustatus
lustatus(1M) System Administration Commands lustatus(1M)
NAME
lustatus - display status of boot environments
SYNOPSIS
/usr/sbin/lustatus [-l error_log] [-o outfile] [BE_name] [-X]
DESCRIPTION
The lustatus command is part of a suite of commands that make up the Live Upgrade feature of the Solaris operating environment. See
live_upgrade(5) for a description of the Live Upgrade feature.
The lustatus command displays the status information of the boot environment (BE) BE_name. If no BE is specified, the status information
for all BEs on the system is displayed.
The headings in the lustatus information display are described as follows:
Boot Environment Name
Name of the BE.
Is Complete
Indicates whether a BE is able to be booted. Any current activity or failure in an lucreate(1M) or luupgrade(1M) operation causes a BE
to be incomplete. For example, if there is a copy operation proceeding on or scheduled for a BE, that BE is considered incomplete.
Active Now
Indicates whether the BE is currently active. The "active" BE is the one currently booted.
Active On Reboot
Indicates whether the BE becomes active upon next reboot of the system.
Can Delete
Indicates that no copy, compare, or upgrade operations are being performed on a BE. Also, none of that BE's file systems are currently
mounted. With all of these conditions in place, the BE can be deleted.
Copy Status
Indicates whether the creation or repopulation of a BE is scheduled or active (that is, in progress). A status of ACTIVE, COMPARING
(from lucompare(1M)), UPGRADING, or SCHEDULED prevents you performing Live Upgrade copy, rename, or upgrade operations.
The following is an example lustatus display:
Boot Environment Is Active Active Can Copy
Name Complete Now On Reboot Delete Status
-------------------- -------- ------ --------- ------ ----------
disk_a_S7 yes yes yes no -
disk_b_S7db yes no no no UPGRADING
disk_b_S8 no no no no -
S9testbed yes no no yes -
Note that you could not perform copy, rename, or upgrade operations on disk_b_S8, because it is not complete, nor on disk_b_S7db, because a
Live Upgrade operation is pending.
The lustatus command requires root privileges.
OPTIONS
The lustatus command has the following options:
-l error_log
Error and status messages are sent to error_log, in addition to where they are sent in your current environment.
-o outfile
All command output is sent to outfile, in addition to where it is sent in your current environment.
-X
Enable XML output. Characteristics of XML are defined in DTD, in /usr/share/lib/xml/dtd/lu_cli.dtd.<num>, where <num> is the version
number of the DTD file.
OPERANDS
BE_name
Name of the BE for which to obtain status. If BE_name is omitted, lustatus displays status for all BEs in the system.
EXIT STATUS
The following exit values are returned:
0 Successful completion.
>0 An error occurred.
FILES
/etc/lutab
list of BEs on the system
/usr/share/lib/xml/dtd/lu_cli.dtd.<num>
Live Upgrade DTD (see -X option)
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWluu |
+-----------------------------+-----------------------------+
SEE ALSO
lu(1M), luactivate(1M), lucancel(1M), lucompare(1M), lucreate(1M), lucurr(1M), ludesc(1M), ludelete(1M), lufslist(1M), lumake(1M),
lumount(1M), lurename(1M), luupgrade(1M), lutab(4), attributes(5), live_upgrade(5)
SunOS 5.10 23 Apr 2003 lustatus(1M)