Sponsored Content
Operating Systems SCO Strange behaviour on Openserver 5.0.2 after 09/2015 Post 302954472 by ChipperEs on Tuesday 8th of September 2015 09:17:29 AM
Old 09-08-2015
yes, i have a test system. every week, the system is been shut down and backup-ed automatically. that is why the clean startup with the right date is necessary.

/usr/adm/messages contains only the spalsh screen from the startup, and the .log files in /etc/rc2.d/messages contain only the messages with fork failed - too many processes.

the non-sco software running on the server is loaded by S99, long after the first fork failed message apperars

---------- Post updated at 08:17 AM ---------- Previous update was at 07:44 AM ----------

by the way, on normal startup the first message appears after "Starting TCP services: snmpd routed"
 

9 More Discussions You Might Find Interesting

1. Linux

/etc/passwd strange behaviour!

Hi there, first of all, here is my conf of a uname -a Linux SAMBA 2.4.18-4GB #1 Wed Mar 27 13:57:05 UTC 2002 i686 unknown on a fedora machine. Here is my problem: every once in a while, the line containing root disappears in the /etc/passwd, disabling all logging on my server. Any one have... (0 Replies)
Discussion started by: penguin-friend
0 Replies

2. Shell Programming and Scripting

A Strange Behaviour!!!

Can some-one give me a view to this : I have a directory in an unix server, having permissions r-xr-xr-x .This directory is basically a source directory. Now there is another directory basically the destination directory which has all the permissions. Note:I log in as not the owner,but user... (5 Replies)
Discussion started by: navojit dutta
5 Replies

3. UNIX for Advanced & Expert Users

Strange sed behaviour

$ echo a.bc | sed -e "s/\|/\\|/g" |a|.|b|c| $ Is the behavior of the sed statement expected ? Or is this a bug in sed ? OS details Linux 2.6.9-55.0.0.0.2.ELsmp #1 SMP Wed May 2 14:59:56 PDT 2007 i686 i686 i386 GNU/Linux (8 Replies)
Discussion started by: vino
8 Replies

4. UNIX for Dummies Questions & Answers

Strange Program behaviour

Had a strange thing going on with my code. It's ok I figured it out for myself.... (2 Replies)
Discussion started by: mrpugster
2 Replies

5. Shell Programming and Scripting

strange behaviour from sed???

Hi all, I want to do a very simple thing with sed. I want to print out the line number of a disk I have defined in /etc/exports, so I do: It's all good, but here's the problem. When I define md0 in a variable, I get nothing from sed: Why is that? can anybody please help? Thanks (2 Replies)
Discussion started by: alirezan
2 Replies

6. Shell Programming and Scripting

Strange behaviour with perl i/o?

Hi All, I got a strange problem here. I have a perl script which is fetching data from a database table and writing a file with that data. If i run that script from linux command line, the file it creates is a normal ascii text file without any binary character in it.But... (9 Replies)
Discussion started by: DILEEP410
9 Replies

7. HP-UX

Strange login behaviour

Hi all, I am using HP-UX and I have just noticed that when I log into the network it seems to save the previous windows that were subsequently closed on previous occasions. Does anyone know when I log in, it seems to display these previous windows, e.g. nedit windows open again? Does... (1 Reply)
Discussion started by: cyberfrog
1 Replies

8. Shell Programming and Scripting

Strange RegExp Behaviour

Hello, I was trying to identify lines who has a word of the following pattern "xyyx" (where x, and ys are different characters). I was trying the following grep - egrep '(\S)()\2\1' This pattern do catches the wanted pattern, but it also catches "GGGG" or "CCCC" patterns. I was trying to... (5 Replies)
Discussion started by: itskov
5 Replies

9. Red Hat

Crontab strange behaviour

Hi all, I'm having this scenario which for the moment I cannot resolve. :( I wrote a script to make a dump/export of the oracle database. and then put this entry on crontab to be executed daily for example. The script is like below: cat /home/oracle/scripts/db_backup.sh #!/bin/ksh ... (3 Replies)
Discussion started by: enux
3 Replies
USERVD(8)						    BSD System Manager's Manual 						 USERVD(8)

NAME
uservd -- supply user services SYNOPSIS
userv [-daemon] DESCRIPTION
uservd is the daemon called by userv to have a task performed under different userid while maintaining limited trust between caller and callee. OPTIONS
There is one optional argument: -daemon Requests that the program daemonise. If this flag is supplied, uservd will fork and completely detach from the controlling ter- minal. If this option is not supplied, uservd will remain in its starting process group and continue to use the supplied stderr stream for any runtime system messages; this is useful for running uservd as a child of init. Errors detected by uservd itself will be reported via syslog in either case. SYSLOG MESSAGES
: uservd issues diagnostics of various kinds to syslog, with facility LOG_DAEMON. The syslog levels used are: debug Verbose messages about the activity of the userv daemon. info Two log messages about the nature and outcome of each request. notice Messages about the status of the daemon, including the startup message and the hourly socket check messages. warning If the uservd exits because it believes that it no longer controls the rendezvous socket (ie, its socket has become orphaned), this level will receive messages indicating why the daemon believes this and notifying of its shutdown. err A believed-recoverable error condition was detected by the userv server in itself, the client or the operating system (this includes resource shortages). The uservd will try to continue. crit The uservd detected a non-recoverable error condition after startup and will exit. alert not used. emerg not used. The service configuration language has the facility to direct error and warning messages to syslog. The default facility and level is user.err, but the author of the configuration file(s) can override this. EXIT STATUS
The daemon's exit code will reflect how well things went: 0 The daemon was asked to detach itself from the controlling terminal and this appears to have been done successfully. 1* The daemon got a SIGTERM or SIGINT and shut itself down. 2* The daemon believed that it was no longer the uservd and so exited to clean up. 3 uservd was started with incorrect arguments. 4 A system call failure or other environmental problem occurred during startup. 5* There was a non-recoverable error after startup; the uservd had to exit. 6 The daemon was asked to detach itself, but its detaching child died for some unexpected reason. SIGABRT/SIGIOT* An unexpected internal error, usually caused by a bug in uservd. This can also occur if an attempt to block signals using sig- procmask fails. Outcomes marked * are not possible if the daemon is asked to detach itself - these exit statuses will be reaped by init instead and so will not usually be logged anywhere. The daemon's per-request children will report the success or otherwise of its request in their exit status. These are not usually be logged unless they indicate a serious problem. ENVIRONMENT
All of the environment variables passed to uservd will be inherited by services as part of the default environment. (If the set-environment configuration directive is used, then other system configuration files can modify the environment. Consult the specification.) SEE ALSO
userv(1) init(8) Ian Jackson, User service daemon and client specification. COPYRIGHT
GNU userv, including this manpage, is Copyright (C)1996-2003,2006 Ian Jackson, except that the userv(1) manpage is Copyright (C)2000 Ben Har- ris and Copyright (C)2003 Ian Jackson. GNU userv is licensed under the terms of the GNU General Public Licence, version 2 or (at your option) any later version, and it comes with NO WARRANTY, not even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for details. You should have received a copy of the GNU General Public License along with userv, if not, write to the Free Software Foundation, 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. HISTORY
uservd was initially written in 1996 by Ian Jackson. It became GNU uservd in 1999, and version 1.0 was released in 2000. userv November 3, 1999 userv
All times are GMT -4. The time now is 06:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy