9 More Discussions You Might Find Interesting
1. Solaris
Hi all, I have a LUN that is in "Online Busy" when I issue the dev_gestate subcommand of luxadm:
root@es088wb6:~# luxadm -v -e dev_getstate /dev/rdsk/c21t50050763090887FEd4s2
phys path = "/devices/pci@6c0/pci@1/pci@0/pci@4/SUNW,qlc@0/fp@0,0/ssd@w50050763090887fe,4:c,raw"
... (5 Replies)
Discussion started by: ludiegu
5 Replies
2. Solaris
Hey there,
I joined this forum just now cause I need help with an old SUN machine at work. I work on a helpdesk and we use a SOLARIS 5.10 OS. Every once in a while we will try to move one of our windows out of the way to make room on the desktop, and sometimes the mouse doesn't release what we... (7 Replies)
Discussion started by: TRex_2005
7 Replies
3. Solaris
Hi Community,
i have one M5000 spare machine which was handled by support team. they told me that it is gone completely .
i have checked the status. before it was showing MBU_B degraded. i updated to latest firmware and , resetted the xscf and now this is showing as normal.
MBU_B... (5 Replies)
Discussion started by: bentech4u
5 Replies
4. IP Networking
Server is stuck at "Stuck at "bringing up interface eth0:""
after i hard reset the server
I have IPMI access, please help me diagnose the cause if you can :( (0 Replies)
Discussion started by: postcd
0 Replies
5. BSD
Hi Experts,
I am executing "svn" checkout command through my java code on a freeBSD machine. SVN checkout gets started , but when I run "top" command on my freebsd machine, I have observed that "svn" processes are stuck in "pipewr" state.
Any pointer for this problem?
Thanks,
akash (0 Replies)
Discussion started by: akash.mahakode
0 Replies
6. Shell Programming and Scripting
Hi,
I have line in input file as below:
3G_CENTRAL;INDONESIA_(M)_TELKOMSEL;SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL
My expected output for line in the file must be :
"1-Radon1-cMOC_deg"|"LDIndex"|"3G_CENTRAL|INDONESIA_(M)_TELKOMSEL"|LAST|"SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL"
Can someone... (7 Replies)
Discussion started by: shis100
7 Replies
7. AIX
Hi
I was wondering if anybody has come across in a failure of fuser command.
We have a backup script that is:
fuser -c -k /XXX/XXXXXXX
sync;sync
umount /XXX/XXXXXXX/
backup -0 -f /dev/rmt0.1 -u /dev/XXXXXXXlv
mount /XXX/XXXXXXX/
sync;sync
The script is called from crontab via an... (2 Replies)
Discussion started by: ggovotsis
2 Replies
8. Solaris
On Solaris 8, when I do a lpstat -o:
I have tried cancel 140828p-16974, but the entries remain
New prints to this printer and others work successfully.
Can anyone suggest how to get rid of these entries.
Thanks (2 Replies)
Discussion started by: pmm
2 Replies
9. AIX
Good afternoon,
I'm currently working on an IBM 9110-510, with an AIX 6.1 on it.
Currently, I've put an HyperTerminal on the machine vty0. Folowing the procedure given by a support guy(§details), I'm able to get to the AIX banner
... (6 Replies)
Discussion started by: nilleb
6 Replies
SVN-AUTORELEASEDEB(1) User Contributed Perl Documentation SVN-AUTORELEASEDEB(1)
NAME
svn-autoreleasedeb - Automatic Release of debian packages from
DESCRIPTION
This script generates and uploads the debian package for svn modules managed by svn-buildpackage.
svn-autoreleasedeb will maintain a state file of all the packages you want to be automatically published, and every time you commit the
debian/changelog file of your package, changing the debian version to a greater value, it will be published.
All the parameters to the script are configured in the conffile. There is no command-line switch. See svn-autoreleasedeb.conf(5) for more
information.
USING
There are two ways of using this script:
1) Run as user svn-autoreleasedeb in cron. This is very useful for software houses that want to have the "nightily build" version of the
software published automatically. In this case, the config file will be "/etc/svn-autoreleasedeb.conf" and it will use
/var/lib/svn-autoreleasedeb/ as scratch dir.
NOTE: edit /etc/default/svn-autoreleasedeb to control this behavior
NOTE 2: all output will be thrown in /var/log/svn-autoreleasedeb/run.log
2) Run as yourself, it will automatizate the work you will have if you have your packages in SVN. In this case, the config file will be
$HOME/.svn-autoreleasedeb/conf and the scratch dir will be $HOME/.svn-autoreleasedeb. svn-autoreleasedeb will not create defaults, you
must have the configuration file created before running svn-autoreleasedeb. See svn-autoreleasedeb.conf(5).
TODO
- Use a snapshot of the time of the commit in
the changelog to checkout the source
- Localize the messages.
- Work with other than all lowercase in conffile.
- Use a better format for conffile.
_EXIT CODES
_exit codes:
0 = Clean _exit
1 = Config file not found
2 = No packages in config file
3 = Couldn't open the state file
4 = Couldn't open the state file for writing
5 = Couldn't determine architecture
SEE ALSO
svn-buildpackage(1), svn(1), svn-autoreleasedeb.conf(5), dupload(1)
AUTHOR
This manual page was written by Daniel Ruoso <daniel@ruoso.com>, for the Debian GNU/Linux system.
perl v5.8.7 2006-08-16 SVN-AUTORELEASEDEB(1)