Sponsored Content
Top Forums Shell Programming and Scripting Fdisk and grep command not working in udev trigger Post 303023191 by lxdorney on Wednesday 12th of September 2018 07:11:24 PM
Old 09-12-2018
Quote:
Originally Posted by Scott
"Supposedly" doesn't really instil confidence Smilie You tried setting DEVNAME manually, and that also didn't work?

Is all of the code in the same script.. e.g. did you export DEVNAME if it's not?

If you set DEVNAME manually, after (or in place of) the fdisk command, there's no reason that the output would be
Code:
mount /media/usb/test

instead of
Code:
mount /dev/sdb1 /media/usb/test

If the variable DEVNAME is not created as read-only, or you're not running the script in a shell jail, that is.
Yes Sir you right the output
Code:
mount /dev/sdb1 /media/usb/test

but mounting is not working
 

10 More Discussions You Might Find Interesting

1. Linux

udev core 5

installed fedora core 5 on a pc with USB and some usual things. in boot up it is stopped at "Starting udev:". Its harddisk light is busy. is it reconfiguring the kernel?. what do to solve this problem?. (0 Replies)
Discussion started by: GJ2
0 Replies

2. Shell Programming and Scripting

How can I trigger another make command when one is finished?

Hello all I have to run manually make commands in our system the make compilations task's takes very long And I like to be able to run another make task right after one is finished. What is the best way to automate it ? (2 Replies)
Discussion started by: umen
2 Replies

3. Shell Programming and Scripting

Fdisk with grep problem

Hello! rescuecd:/var# fdisk -l | grep stupid Disk /dev/sda doesn't contain a valid partition table Disk /dev/sdb doesn't contain a valid partition table rescuecd:/var# It shows always this statement. Why? :( Raw fdisk -l shows rescuecd:/var# fdisk -l Disk /dev/sda: 750.1 GB,... (4 Replies)
Discussion started by: pug123
4 Replies

4. Shell Programming and Scripting

Grep command is not working when put into cron

Hi, I worte a script which runs perfect when i execute it manually. But when i scheduled into cron the grep command alone is not working. the sample script, /usr/bin/grep FTP $subfile > /tmp/tfsrec.dat tfs=`echo $?` if then echo "FTP FOUND" else echo "FTP NOT FOUND" Where... (5 Replies)
Discussion started by: thiru_cs
5 Replies

5. Filesystems, Disks and Memory

Udev label removes corresponding fdisk, sfdisk or lsvdev entry

I'm curious about the behavior where any udev labeled device causes that corresponding listing to disappear from fdisk, sfdisk, or in the case of RDAC, lsvdev. I have seen this on both EMC clariion and Sun Storagetek/Engenio 6540 arrays. We use RHEL5.1 and udev to create persistent labels for... (2 Replies)
Discussion started by: Radar
2 Replies

6. Shell Programming and Scripting

Pass params with Udev

Hello! I'm sorry if this is the false Forum, didn't really knew where to put it... My question: I have serveral USB-Sticks and wrote several Udev-Rules for theme, each Sticks needs to do something else, but all are using the same script (they have common tasks to do) and only some parts are... (2 Replies)
Discussion started by: al0x
2 Replies

7. Solaris

what is the fdisk -l command of SUN

I use fdisk -l command to see the attached hard disk drives in rhel5 and cntos 5.5 what is the same command for sun 5.9 (4 Replies)
Discussion started by: z_haseeb
4 Replies

8. Shell Programming and Scripting

problem in automating "fdisk" command using send and expect

hi i want to automate fdisk command . i spawned a process containing fdisk command from a process and tried to send the options to fdisk promt from that process. but that spawed process is notstarting itself help me out trying for two days :wall: my code: #!/bin/bash echo... (5 Replies)
Discussion started by: jagak89
5 Replies

9. BSD

OpenBSD fdisk - Linux fdisk compatibility ?

Hello, MBR partition table made by linux fdisk looks certainly not correct when printed by openbsd fdisk: Partition table created on linux (centos 6.3): # fdisk -l /dev/sdc Disk /dev/sdc: 10.7 GB, 10737418240 bytes 255 heads, 63 sectors/track, 1305 cylinders Units = cylinders of 16065 *... (2 Replies)
Discussion started by: vilius
2 Replies

10. UNIX for Beginners Questions & Answers

Grep command is not working

I have made a program that reads a text file and checks for palindromic words and then outputs them. They each appear on a new line with a count of the number of occurences beside each of the words. Requirements for being classed as palindrome are that the word must have at least 3 letters and... (7 Replies)
Discussion started by: greenhouse91
7 Replies
vfstab(4)                                                          File Formats                                                          vfstab(4)

NAME
vfstab - table of file system defaults DESCRIPTION
The file /etc/vfstab describes defaults for each file system. The information is stored in a table with the following column headings: device device mount FS fsck mount mount to mount to fsck point type pass at boot options The fields in the table are space-separated and show the resource name (device to mount), the raw device to fsck (device to fsck), the default mount directory (mount point), the name of the file system type (FS type), the number used by fsck to decide whether to check the file system automatically (fsck pass), whether the file system should be mounted automatically by mountall (mount at boot), and the file system mount options (mount options). (See respective mount file system man page below in SEE ALSO for mount options.) A '-' is used to indicate no entry in a field. This may be used when a field does not apply to the resource being mounted. The getvfsent(3C) family of routines is used to read and write to /etc/vfstab. /etc/vfstab can be used to specify swap areas. An entry so specified, (which can be a file or a device), will automatically be added as a swap area by the /sbin/swapadd script when the system boots. To specify a swap area, the device-to-mount field contains the name of the swap file or device, the FS-type is "swap", mount-at-boot is "no" and all other fields have no entry. EXAMPLES
The following are vfstab entries for various file system types supported in the Solaris operating environment. Example 1: NFS and UFS Mounts The following entry invokes NFS to automatically mount the directory /usr/local of the server example1 on the client's /usr/local directory with read-only permission: example1:/usr/local - /usr/local nfs - yes ro The following example assumes a small departmental mail setup, in which clients mount /var/mail from a server mailsvr. The following entry would be listed in each client's vfstab: mailsvr:/var/mail - /var/mail nfs - yes intr,bg The following is an example for a UFS file system in which logging is enabled: /dev/dsk/c2t10d0s0 /dev/rdsk/c2t10d0s0 /export/local ufs 3 yes logging See mount_nfs(1M) for a description of NFS mount options and mount_ufs(1M) for a description of UFS options. Example 2: pcfs Mounts The following example mounts a pcfs file system on a fixed hard disk on an x86 machine: /dev/dsk/c1t2d0p0:c - /win98 pcfs - yes - The example below mounts a Jaz drive on a SPARC machine. Normally, the volume management daemon (see vold(1M)) handles mounting of remov- able media, obviating a vfstab entry. If you choose to specify a device that supports removable media in vfstab, be sure to set the mount- at-boot field to no, as below. Such an entry presumes you are not running vold. /dev/dsk/c1t2d0s2:c - /jaz pcfs - no - For removable media on a SPARC machine, the convention for the slice portion of the disk identifier is to specify s2, which stands for the entire medium. For pcfs file systems on x86 machines, note that the disk identifier uses a p (p0) and a logical drive (c, in the /win98 example above) for a pcfs logical drive. See mount_pcfs(1M) for syntax for pcfs logical drives and for pcfs-specific mount options. Example 3: CacheFS Mount Below is an example for a CacheFS file system. Because of the length of this entry and the fact that vfstab entries cannot be continued to a second line, the vfstab fields are presented here in a vertical format. In re-creating such an entry in your own vfstab, you would enter values as you would for any vfstab entry, on a single line. device to mount: svr1:/export/abc device to fsck: /usr/abc mount point: /opt/cache FS type: cachefs fsck pass: 7 mount at boot: yes mount options: local-access,bg,nosuid,demandconst,backfstype=nfs,cachedir=/opt/cache See mount_cachefs(1M) for CacheFS-specific mount options. Example 4: Loopback File System Mount The following is an example of mounting a loopback (lofs) file system: /export/test - /opt/test lofs - yes - See lofs(7FS) for an overview of the loopback file system. SEE ALSO
fsck(1M), mount(1M), mount_cachefs(1M), mount_hsfs(1M), mount_nfs(1M), mount_tmpfs(1M), mount_ufs(1M), swap(1M), getvfsent(3C) System Administration Guide: Basic Administration SunOS 5.10 21 Jun 2001 vfstab(4)
All times are GMT -4. The time now is 08:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy