Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Which Sendmail version ? and why -d isn't working Post 302253757 by saariko on Sunday 2nd of November 2008 09:24:16 AM
Old 11-02-2008
Power solved

Weird as it may be, I have no clue what I have done, but it works now.

problem solved.
 

10 More Discussions You Might Find Interesting

1. Solaris

grep -r isn't working

Hi, I was trying to use this particular option of grep grep -r 'Search_pattern' * This command should ideally search all the occurrences of Search_pattern recursively within a directory & print it on shell prompt. But this command is not doing what is expected. It just displays nothin! ... (8 Replies)
Discussion started by: harishmitty
8 Replies

2. UNIX for Dummies Questions & Answers

Why isn't this working? tsch-doit file

#! /usr/tsch foreach f (`cat contacts.list`) awk '{printf ($2 in a) ? ","$5 : (NR>1) ? RS $2 FS $5 : $2 FS $5; a} END{print e}' $f > $f_inter.map end My file: cat contacts.list is just a list of files. I get this error: doit_contacts2intermap.sh: Command not found. Thanks! (1 Reply)
Discussion started by: lost
1 Replies

3. Shell Programming and Scripting

a very basic sed one-liner...that isn't working :-(

Greetings all. :) I would like to use sed to join all non-blank lines together in a particular file. I was thinking I could do this by simply replacing the terminating, new-line character on every line which is not blank, but I must be missing something in my sed line: $ sed... (3 Replies)
Discussion started by: SteveB-in-LV
3 Replies

4. OS X (Apple)

Canot find library on compile - fixing PKG_CONFIG_PATH isn't working

I am using bash on OSX Leopard. When I attempt ./configure I get this error: checking for OPENSSL... configure: error: Package requirements (openssl) were not met: No package 'openssl' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a... (2 Replies)
Discussion started by: reasonstoprefer
2 Replies

5. Shell Programming and Scripting

awk isn't working

awk 'BEGIN{print '1.2449'**0.5}' awk: line 1: syntax error at or near * can someone help me troubleshoot the above command? i'm trying to do the square root of 1.2449. this command works on Red Hat, but for some reasonn isn't working on kubuntu (latest version). shell is bash. i... (3 Replies)
Discussion started by: SkySmart
3 Replies

6. Shell Programming and Scripting

crontab - runninf a java script just isn't quite working...

hi gurus. I have a little script that runs java from a certain directory. This script runs fine when run manually but when I try to schedule it, it fails to find the script. little_script.sh.. /<directory of java>/java -classpath... (3 Replies)
Discussion started by: MrCarter
3 Replies

7. Shell Programming and Scripting

String == isn't working in [[-test

Hi. I'm new to this forum, my English perhaps is not so good, but here is my question: In bash you can use ] for tests, and how I understand it the variable names should be expanded automatically. So this should give "yes": xx=hello $ ] && echo yes || echo no no # not giving "yes" These two... (2 Replies)
Discussion started by: 244an
2 Replies

8. Shell Programming and Scripting

export of a variable isn't working

Hi I want export input data ... echo "month: " read m export m=$m also export m is not working ? the month-variable should be exportet for the use in other scripts, but it is not working like this. What i'm doing wrong? Thanks in advance! IMPe (10 Replies)
Discussion started by: IMPe
10 Replies

9. Shell Programming and Scripting

Chmod working in sudo run script but chown isn't

My git user has permission in sudoers to run a wrapper script to move files into my webroot. Everything is working fine except for the chown line. After the script has run, the files ar still root:root instead of apache:apache. Scratching my head...:confused: #!/bin/sh echo echo "****... (4 Replies)
Discussion started by: dheian
4 Replies

10. HP-UX

Syslog daemon isn't working

Hi All, I've tried starting syslogd on our hp-ux 11.31 server. However, it is not getting started nor it is updating the syslog file. There is no space issue also. However, the mail.log file is approx 2GB, can that be of any issue. Please find the details below: # /sbin/init.d/syslogd... (2 Replies)
Discussion started by: Kits
2 Replies
SI(4)							   BSD Kernel Interfaces Manual 						     SI(4)

NAME
si, sw -- NCR 5380 SCSI bus host adaptor driver SYNOPSIS
sun3 si0 at obio0 addr 0x140000 ipl 2 sun3 and sun3x si0 at vme2 addr 0x200000 ipl 2 vect 0x40 si1 at vme2 addr 0x204000 ipl 2 vect 0x41 sun3/E sebuf0 at vme2 addr 0x300000 ipl 2 vect 0x74 # and 0x75 sebuf1 at vme2 addr 0x340000 ipl 2 vect 0x76 # and 0x77 si* at sebuf? sun4 and sun2 si0 at vme0 addr 0x200000 pri 2 vec 0x40 sun4/100 sw0 at obio0 addr 0x0a000000 level 3 DESCRIPTION
The si and sw "SCSI Weird" drivers provide support for the NCR 5380 SCSI Bus Controller (SBC) chip found on various Sun Microsystems CPU motherboards (obio), and on the "Sun-3 VME SCSI" (Sun part # 501-1236) board used in systems with VME bus. sun3 and sun3x The sun3 and sun3x version of this driver can be configured with a flags directive in the config(1) file. The values are bits in a bitfield, and are interpreted as follows: 0x000ff Set bit (1<<target) to disable SCSI disconnect/reselect 0x0ff00 Set bit (1<<(target+8)) to disable SCSI parity checking 0x10000 Set this bit to disable DMA interrupts (poll) 0x20000 Set this bit to disable DMA entirely (use PIO) For example: "flags 0x1000f" would disable DMA interrupts, and disable disconnect/reselect for targets 0-3. The "target" is the SCSI ID num- ber of a particular device on a particular SCSI bus. sun4 The sun4 version of this driver can also be configured with a flags directive in the config(1) file. The values are bits in a bitfield, and are interpreted as follows: 0x01 Use DMA (may be polled) 0x02 Use DMA completion interrupts 0x04 Allow SCSI disconnect/reselect For example: "flags 0x07" would enable DMA, interrupts, and reselect. By default, DMA is enabled in the sun4 driver. SEE ALSO
cd(4), ch(4), intro(4), scsi(4), sd(4), st(4) AUTHORS
David Jones, Gordon Ross <gwr@NetBSD.org>, Adam Glass <glass@NetBSD.org>, Jason R. Thorpe <thorpej@NetBSD.org>. BUGS
The VME variant has a bit to enable or disable the DMA engine, but that bit also gates the interrupt line from the NCR5380 (!!). Therefore, in order to get any interrupt from the NCR5380, (i.e. for reselect) one must clear the DMA engine transfer count and then enable DMA. This has the further complication that you CAN NOT touch the NCR5380 while the DMA enable bit is set, so we have to turn DMA back off before we even look at the NCR5380. Support for the Sun 4/100 sw "SCSI Weird" is not complete. DMA works, but interrupts (and, thus, reselection) don't for reasons unknown. Further progress has halted pending the availability of a machine for testing. DMA, DMA completion interrupts, and reselection work fine on a Sun 4/260 with modern SCSI-II disks attached. There have been reports of res- election failing on Sun Shoebox-type configurations where there are multiple non-SCSI devices behind Emulex or Adaptec bridges. These devices pre-date the SCSI-I spec, and might not behave the way the NCR5380 code expects. For this reason, only DMA is enabled by default in the sun4 driver. BSD
May 7, 1998 BSD
All times are GMT -4. The time now is 03:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy