Sponsored Content
Full Discussion: Remote Boot
Operating Systems Linux SuSE Remote Boot Post 302099394 by stdout on Monday 11th of December 2006 11:40:36 PM
Old 12-12-2006
well,

surely - you can wake modern x86/x64 by phone if your machine have a modem and does support wake on ring .
but at this topic "maybe" - the point is that we must have PXE capable NIC right - to support wake on LAN?
DHCP + TFTP + boot file/image - etc.
but - actually its all about apps (terminal/remote install etc) that runs on top of it.
i mean - why you wake the machine if you dont have anything to do with it?

cheersSmilie
 

9 More Discussions You Might Find Interesting

1. Red Hat

linux will not boot, boot to grub prompt

my redhat 9 will not boot. We had a power failure and when the power came back, my redhat linux will not boot. The machine come up to grub prompt. I tried the following from grub prompt root (hd0, then press tab key partition num:0 filesystem type unknown, partition type 0x83... (7 Replies)
Discussion started by: hassan2
7 Replies

2. UNIX for Advanced & Expert Users

Cannot boot - Boot : Panic : File size out of range (EWS-UX/V unix)

Hey ! I am running EWS-UX/V (Rel 4.2) on NEC EWS/4800/330 station and I am having problems rebooting my station : I am getting the following message on display : BOOT : PANIC : File size out of range. According to user guide, this error is occuring when a file exceeding the limit and/or... (2 Replies)
Discussion started by: fredo
2 Replies

3. Solaris

solaris boot problem boot error loading interpreter(misc/krtld)

When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error. cannot find mis/krtld boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies

4. UNIX for Dummies Questions & Answers

Boot from a remote system

I have a diskless work station. i want to boot from a remote linux machine. what changes i will have to do in configuration. Plz tell me thanks (1 Reply)
Discussion started by: hemant29
1 Replies

5. Solaris

cannot find boot device and won't boot off cdrom

I'm running solaris 2.5.1. My main development server is DEAD, i can't even boot off the cdrom, it powers up, acts like it is starting the boot process but then says cannot find boot device. I've done the search here on this site and saw the other posts, but at the ok prompt it won't even let me... (3 Replies)
Discussion started by: kymberm
3 Replies

6. SCO

stage 1 boot failure: error loading hd (40)/boot

hi SCO Unix 5.0.6 doesn't boot due to this problem: not a directory boot not found cannot open stage 1 boot failure: error loading hd (40)/boot Knows someone howto solve it? (16 Replies)
Discussion started by: ccc
16 Replies

7. Boot Loaders

Reboot and Select Proper Boot device or insert Boot media in select Boot device and press a key

Hello, I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error " reboot and select proper Boot device or insert Boot media in select Boot device and press a key " I have tried CD and... (0 Replies)
Discussion started by: rpf
0 Replies

8. Solaris

Solaris x86 installation using jumpstart does not local boot ( boot from hdd)

I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies

9. Red Hat

RHEL6 Diskless Remote boot fail

Hi guys, I've been trying to set up a server for disk-less booting of remote machines on a network. The server host OS is RHEL6 and I have configured dhcp, tftp and nfs services which are proven to be working since I am able to install RHEL6 through pxe boot. Now I want it to serve for disk-less... (0 Replies)
Discussion started by: aninmuk
0 Replies
SD_LOGIN_MONITOR_NEW(3)                                        sd_login_monitor_new                                        SD_LOGIN_MONITOR_NEW(3)

NAME
sd_login_monitor_new, sd_login_monitor_unref, sd_login_monitor_flush, sd_login_monitor_get_fd - Monitor login sessions, seats and users SYNOPSIS
#include <systemd/sd-login.h> int sd_login_monitor_new(const char* category, sd_login_monitor** ret); sd_login_monitor* sd_login_monitor_unref(sd_login_monitor* m); int sd_login_monitor_flush(sd_login_monitor* m); int sd_login_monitor_get_fd(sd_login_monitor* m); DESCRIPTION
sd_login_monitor_new() may be used to monitor login session, users and seats. Via a monitor object a file descriptor can be integrated into an application defined event loop which is woken up each time a user logs in, logs out or a seat is added or removed, or a session, user, or seat changes state otherwise. The first parameter takes a string which can be either seat (to get only notifications about seats being added, removed or changed), session (to get only notifications about sessions being created or removed or changed) or uid (to get only notifications when a user changes state in respect to logins). If notifications shall be generated in all these conditions, NULL may be passed. Note that in future additional categories may be defined. The second parameter returns a monitor object and needs to be freed with the sd_login_monitor_unref() call after use. sd_login_monitor_unref() may be used to destroy a monitor object. Note that this will invalidate any file descriptor returned by sd_login_monitor_get_fd(). sd_login_monitor_flush() may be used to reset the wakeup state of the monitor object. Whenever an event causes the monitor to wake up the event loop via the file descriptor this function needs to be called to reset the wake-up state. If this call is not invoked the file descriptor will immediately wake up the event loop again. sd_login_monitor_get_fd() may be used to retrieve the file descriptor of the monitor object that may be integrated in an application defined event loop, based around poll(2) or a similar interface. The application should include the returned file descriptor as wake up source for POLLIN events. Whenever a wake-up is triggered the file descriptor needs to be reset via sd_login_monitor_flush(). An application needs to reread the login state with a function like sd_get_seats(3) or similar to determine what changed. RETURN VALUE
On success sd_login_monitor_new() and sd_login_monitor_flush() return 0 or a positive integer. On success sd_login_monitor_get_fd() returns a Unix file descriptor. On failure, these calls return a negative errno-style error code. sd_login_monitor_unref() always returns NULL. NOTES
The sd_login_monitor_new(), sd_login_monitor_unref(), sd_login_monitor_flush() and sd_login_monitor_get_fd() interfaces are available as shared library, which can be compiled and linked to with the libsystemd-login pkg-config(1) file. SEE ALSO
systemd(1), sd-login(7), sd_get_seats(3) AUTHOR
Lennart Poettering <lennart@poettering.net> Developer systemd 10/07/2013 SD_LOGIN_MONITOR_NEW(3)
All times are GMT -4. The time now is 05:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy